> 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/modules-and-features/program/certificates/certificate-states.md). # Certificate states Learn about the different states of a certificate. A certificate is an object that verifies a client or partner meets a vendor’s requirements and eligibility criteria for a specific program. A certificate can be in one of these states: **Pending**, **Active**, **Expired**, **Updating**, or **Terminated**. The following diagram shows the transitions between these states:

The state transition diagram of a certificate.

The following table describes the different states:

State	Definition
New	This is the initial or starting state. This state is assigned by the platform when the certificate request is created.
Pending	The certificate has been created, and it's awaiting approval by the vendor.
Active	The certificate is active.
Expired	The certificate has expired. You can renew an expired certificate by re-enrolling in the program.
Updating	The certificate is being updated due to re-enrollment in the program.
Terminated	The certificate has been terminated. Terminated certificates can't be used to re-enroll in a program.

--- # 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/modules-and-features/program/certificates/certificate-states.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.