> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anchorage.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Operate

> Track stablecoin conversions and interpret their status.

Once a conversion is submitted, follow it to completion and interpret its status with two read endpoints.

## How to follow a conversion

* [`GET /v2/stablecoins/history`](https://developers.anchorage.com/reference/getstablecoinhistory) — One record per conversion, with status and pointers to the underlying transactions. `operationType` indicates the type of operation carried out.
* [`GET /v2/transactions`](https://developers.anchorage.com/reference/gettransactions) — The underlying ledger entries, filterable by `types`.

For query parameters, example responses, and pagination, see [Track conversion status](/knowledge-base/platform/developers/stablecoins/operate/track-status).

## Status values

| Status      | Meaning                                                                               |
| :---------- | :------------------------------------------------------------------------------------ |
| `INITIATED` | Awaiting endorsements.                                                                |
| `EXECUTING` | Approved, pending settlement.                                                         |
| `COMPLETED` | Conversion settled.                                                                   |
| `FAILED`    | Conversion did not complete.                                                          |
| `UNKNOWN`   | Forward-compatibility fallback—handle gracefully rather than treating it as an error. |

`subStatus` is an optional qualifier on `status`. The only customer-observable value today is `REJECTED_BY_CUSTOMER`, paired with `status: FAILED`.

## Key terms

| Term                                           | Definition                                                                                                     |
| :--------------------------------------------- | :------------------------------------------------------------------------------------------------------------- |
| `authorizationOperationId`                     | Operation ID returned by `/v2/stablecoins/conversion`. Tracks endorsement and approval.                        |
| `issueRedeemId`                                | Unique identifier for the conversion as a whole. Stable across both legs of a bridge.                          |
| `operationType`                                | In `/v2/stablecoins/history`: `MINT`, `BURN`, or `BRIDGE`.                                                     |
| `sourceOperationId` / `destinationOperationId` | Nullable transaction IDs for each leg. Pass to `GET /v2/transactions/{transactionId}` for full ledger details. |
| `status`                                       | `INITIATED`, `EXECUTING`, `COMPLETED`, `FAILED`, or `UNKNOWN`.                                                 |
| `subStatus`                                    | Optional qualifier on `status`. Currently only `REJECTED_BY_CUSTOMER` (with `status: FAILED`).                 |
| `idempotencyKey`                               | Client-supplied string ≤128 characters on `/v2/stablecoins/conversion`. Use a distinct key per conversion.     |

## Idempotency and retries

Provide an `idempotencyKey` per conversion so an interrupted call can be retried safely without double-minting or double-burning. For status codes, rate limits, and cursor pagination, see [Errors and pagination](/knowledge-base/api-reference/errors-pagination).