> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/developer-resources/rest-api/commerce-api/agreements/agreement-state-diagram.md). # State diagram The following diagram shows the state (status) transition process of an agreement within the platform.

The state transition diagram of an agreement.

State	Definition
New	This is the default state of a newly created agreement.
Draft	The agreement has been saved as a draft because the purchase order has been saved for later during the ordering process.
Deleted	The draft agreement has been deleted because the draft purchase order associated with the agreement was deleted.
Provisioning	The agreement has been sent to the vendor and it's pending fulfilment.
Failed	The agreement failed because the vendor or SoftwareOne has canceled the purchase order.
Active	The vendor has completed the purchase order, and the agreement is active. Active agreements have at least one active subscription and no open orders.
Updating	A business transaction or a change order is in progress for at least one subscription within the agreement.
Terminated	The agreement has been terminated. It no longer contains an active subscription.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.platform.softwareone.com/developer-resources/rest-api/commerce-api/agreements/agreement-state-diagram.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.