> 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/api-usage-and-reference/object-diagrams.md).

# Objects diagrams

View the state transition diagrams for various objects in the platform.

View state diagrams for Marketplace Platform objects.

These objects support workflows between [different actors](/marketplace-platform/platform-overview/key-concepts.md#actors), such as clients, partners, and vendors.

This page includes objects that move through statuses during their lifecycle. Objects without statuses, such as audit records and spotlight resources, are not included.

### Object diagrams

Open a section to view the available diagrams for each API.

<details>

<summary>Accounts API</summary>

* [Account](/developer-resources/rest-api/accounts-api/account/state-diagram.md)
* [API Token](/developer-resources/rest-api/accounts-api/api-tokens/token-state-diagram.md)
* [Buyer](/developer-resources/rest-api/accounts-api/buyer/buyer-state-diagram.md)
* [Group](/developer-resources/rest-api/accounts-api/user-groups/group-state-diagram.md)
* [Licensee](/developer-resources/rest-api/accounts-api/licensee/licensee-state-diagram.md)
* [Seller](/developer-resources/rest-api/accounts-api/seller/seller-state-diagram.md)
* [User](/developer-resources/rest-api/accounts-api/users/users-state-diagram.md)

</details>

<details>

<summary>Billing API</summary>

* [Credit Memo](/developer-resources/rest-api/billing-api/credit-memo/state-diagram.md)
* [Custom Ledger](/developer-resources/rest-api/billing-api/custom-ledger-object/state-diagram.md)
* [Invoice](/developer-resources/rest-api/billing-api/invoice/state-diagram.md)
* [Journal](/developer-resources/rest-api/billing-api/journal/state-diagram.md)
* [Statement](/developer-resources/rest-api/billing-api/statement/state-diagram.md)

</details>

<details>

<summary>Catalog API</summary>

* [Authorization](/developer-resources/rest-api/catalog-api/authorization/state-diagram.md)
* [Documentation](/developer-resources/rest-api/catalog-api/documentation/documentation-states.md)
* [Item](/developer-resources/rest-api/catalog-api/items/item-states.md)
* [Listing](/developer-resources/rest-api/catalog-api/listing/state-diagram.md)
* [Media](/developer-resources/rest-api/catalog-api/media/media-states.md)
* [Pricelist](/developer-resources/rest-api/catalog-api/pricelists/pricelist-states.md)
* [Pricelist Item](/developer-resources/rest-api/catalog-api/pricelist-item/pricelist-states.md)
* [Product](/developer-resources/rest-api/catalog-api/product/product-states.md)
* [Terms and Conditions](/developer-resources/rest-api/catalog-api/terms-and-conditions/terms-and-conditions-states.md)

</details>

<details>

<summary>Commerce API</summary>

* [Asset](/developer-resources/rest-api/commerce-api/assets/state-diagram.md)
* [Agreement](/developer-resources/rest-api/commerce-api/agreements/agreement-state-diagram.md)
* [Order](/developer-resources/rest-api/commerce-api/orders/order-state-diagram.md)
* [Request](/developer-resources/rest-api/commerce-api/requests/request-states.md)
* [Subscription](/developer-resources/rest-api/commerce-api/subscriptions/subscription-states.md)

</details>

<details>

<summary>Extensions API</summary>

* [Category](/developer-resources/rest-api/extensions-api/category/state-diagram.md)
* [Extension](/developer-resources/rest-api/extensions-api/extension/state-diagram.md)

</details>

<details>

<summary>Notifications API</summary>

* [Batch](/developer-resources/rest-api/notifications-api/batches/state-diagram.md)
* [Category](/developer-resources/rest-api/notifications-api/categories/state-diagram.md)
* [Contact](/developer-resources/rest-api/notifications-api/contacts/state-diagram.md)
* [Footer](/developer-resources/rest-api/notifications-api/footer/state-diagram.md)
* [Message](/developer-resources/rest-api/notifications-api/messages/notification-state-diagram.md)
* [Template](/developer-resources/rest-api/notifications-api/template/state-diagram.md)
* [Template Variant](/developer-resources/rest-api/notifications-api/template-variant/state-diagram.md)
* [Subscriber](/developer-resources/rest-api/notifications-api/subscribers/state-diagram.md)

</details>

<details>

<summary>Product and Vendor Profiles API</summary>

* [Category](/developer-resources/rest-api/product-catalog-api/category/state-diagram.md)
* [Industry](/developer-resources/rest-api/product-catalog-api/industry/state-diagram.md)
* [Product profile](/developer-resources/rest-api/product-catalog-api/product-profile/state-diagram.md)
* [Segment](/developer-resources/rest-api/product-catalog-api/segment/state-diagram.md)
* [Vendor profile](/developer-resources/rest-api/product-catalog-api/vendor-profile/state-diagram.md)

</details>

<details>

<summary>Program API</summary>

* [Certificates](/developer-resources/rest-api/program-api/certificate/certificate-state-diagram.md)
* [Enrollment](/developer-resources/rest-api/program-api/enrollment/enrollment-state-diagram.md)
* [Program](/developer-resources/rest-api/program-api/program/program-state-diagram.md)

</details>


---

# 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/api-usage-and-reference/object-diagrams.md?ask=<question>&goal=<user_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.