> 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/assets/state-diagram.md). # State diagram An asset is a one-time purchase item or a perpetual license within the Marketplace Platform. An asset can currently exist in these states: **New**, **Draft**, **Active**, or **Terminated**. The following diagram shows the transitions between these states:

State	Definition
New	This is the initial status of an asset or one-time item when it's added to the order during the ordering process. The status appears in the purchase wizard only while creating the order.
Draft	The status applies to an asset during the fulfillment phase of the order. It means the asset has been created as a result of a purchase order, but it's not active yet.
Active	The asset is now active because the associated purchase order has been completed.
Terminated	The asset has been cancelled by the vendor.

--- # 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/assets/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.