# States and Transitions

Every entity in our API has its own state machine and transition rules aiming at helping you to understand the lifecycle of an entity and current state of the integration.

{% content-ref url="/pages/3zksW8JdsRiBuT1LKpnj" %}
[Customer States](/developer-guides/api-integration/states-and-transitions/customer-states.md)
{% endcontent-ref %}

{% content-ref url="/pages/T4x7ckXawQcl0x266zpU" %}
[Account States](/developer-guides/api-integration/states-and-transitions/account-states.md)
{% endcontent-ref %}

{% content-ref url="/pages/Ax3KoIxyvMfzmEH6YSxA" %}
[Card States](/developer-guides/api-integration/states-and-transitions/card-states.md)
{% endcontent-ref %}

{% content-ref url="/pages/KpJmarRks7WQ6YQRfnfu" %}
[Authorisation States](/developer-guides/api-integration/states-and-transitions/authorisation-states.md)
{% endcontent-ref %}

{% content-ref url="/pages/p6zIhu52G9o9h3QeP3e3" %}
[Transaction States](/developer-guides/api-integration/states-and-transitions/transaction-states.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.offblocks.xyz/developer-guides/api-integration/states-and-transitions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.