Track token status

A token’s trading status is a set of restrictions in force, each with an explicit start and end, plus the hours of the underlying market. Restrictions arrive as events; the effective status of a token is one read away.

The effective status

curl "$BASE/tokens/7f3b2c10-5d4e-4a6b-9c8d-1e2f3a4b5c6d/status" -H "Authorization: Bearer $ACCESS_TOKEN"

{
  "tokenId": "7f3b2c10-5d4e-4a6b-9c8d-1e2f3a4b5c6d",
  "assetId": "c0a8e2f4-1b3d-4e5f-8a9b-0c1d2e3f4a5b",
  "marketStatus": "UNAVAILABLE",
  "reason": "TOKEN_PAUSE_COMPLIANCE",
  "activeRestrictions": [
    {
      "restrictionId": "rst_01K7Q4A0D2F4H6J8K0M2P4R6T8", "version": 2,
      "scope": "ASSET", "scopeId": "c0a8e2f4-1b3d-4e5f-8a9b-0c1d2e3f4a5b",
      "restrictionType": "TRADING_SUSPENSION", "reasonCode": "EXCHANGE_SUSPENSION",
      "reasonText": "Suspended by the listing exchange", "source": "LISTING_EXCHANGE", "marketHaltCode": null,
      "effectiveFrom": "2026-10-20T13:57:07.491Z", "expectedEnd": "2026-10-22T13:30:00.000Z",
      "relatedCaId": null, "removedAt": null
    },
    {
      "restrictionId": "rst_01K7Q4C2G4J6L8N0Q2S4V6X8Z0", "version": 1,
      "scope": "TOKEN", "scopeId": "7f3b2c10-5d4e-4a6b-9c8d-1e2f3a4b5c6d",
      "restrictionType": "TOKEN_PAUSE", "reasonCode": "TOKEN_PAUSE_COMPLIANCE",
      "reasonText": null, "source": "SECURITIZE", "marketHaltCode": null,
      "effectiveFrom": "2026-10-20T13:57:12.701Z", "expectedEnd": null,
      "relatedCaId": null, "removedAt": null
    }
  ],
  "asOf": "2026-10-20T14:05:13.439Z"
}

`marketStatus`	Meaning	`reason`
`UNAVAILABLE`	Do not trade. A restriction that stops trading applies to the token, its asset or the underlying market, or the market cannot be read	The `reasonCode` of the most restrictive restriction (`TOKEN_PAUSE` over `WIND_DOWN` over `TRADING_SUSPENSION` over `TRADING_HALT`), or `MARKET_STATUS_UNKNOWN`
`CLOSED`	No restriction; the underlying market is outside regular hours	The market’s reason: `PRE_MARKET`, `POST_MARKET`, or a price-deviation pause such as `FIVE_PERCENT_DEVIATION`
`OPEN`	No restriction; the underlying market is open	`null`

reason mixes two vocabularies: the restriction reason codes when a restriction decides the status, and the market’s own reasons otherwise. Branch on marketStatus first.
Never OPEN by default. When the market status cannot be read, the token is UNAVAILABLE with MARKET_STATUS_UNKNOWN.
SPECIAL_RESTRICTION is listed, not enforced. It appears in activeRestrictions (for example removals-only during an election window) but does not by itself make the token UNAVAILABLE. Read its reasonCode and act on it.
Asset-level view: GET /assets/{assetId}/status lists the ASSET and UNDERLYING_MARKET restrictions only, with no market status.
Filter your tokens by status: GET /tokens?status=UNAVAILABLE or status=OPEN&status=CLOSED filters on marketStatus. It is not the token object’s status (ACTIVE/RETIRED): status=ACTIVE answers 400.

Restrictions as events

Each restriction is one object with its own restrictionId and version, published on every token stream it applies to:

ca.restriction.added     v1   the restriction starts; effectiveFrom
ca.restriction.updated   v2   details changed: expectedEnd, reasonText, marketHaltCode
ca.restriction.removed   v3   the restriction ends; removedAt

Field	What it says
`scope`	`TOKEN`: one token. `ASSET`: every token of the asset. `UNDERLYING_MARKET`: the underlying stock’s market, which also means every token of the asset
`scopeId`	The `tokenId` for `TOKEN`; the `assetId` for `ASSET` and `UNDERLYING_MARKET`. A halt is of the share, not of a chain
`restrictionType`	`TRADING_HALT`, `TRADING_SUSPENSION`, `SPECIAL_RESTRICTION`, `TOKEN_PAUSE`, `WIND_DOWN`
`reasonCode`, `reasonText`	A stable code, and the reason for a human
`source`	`LISTING_EXCHANGE`, `REGULATOR`, `ISSUER`, `SECURITIZE`
`marketHaltCode`	The exchange’s halt code when there is one, for example `T1`
`effectiveFrom`, `expectedEnd`	When it started, and when it is expected to end if announced. `expectedEnd` never ends a restriction
`relatedCaId`	The corporate action that caused it, if any
`removedAt`	Set on the `ca.restriction.removed` version only

Apply restriction events like any other: deduplicate, keep the highest version per restrictionId, replace with data. A restriction is in force from the moment you hold a version without removedAt until you hold one with it.

What to do when one arrives

On ca.restriction.added, stop trading the tokens in scope: the one named for TOKEN, every token of the asset for the other two. Confirm with GET /tokens/{tokenId}/status if you want the computed answer.
On ca.restriction.updated, update what you show; nothing resumes.
On ca.restriction.removed, resume, for that restriction. Another one may still be in force: read activeRestrictions, or keep your own set keyed by restrictionId.

Underlying market signals

For UNDERLYING_MARKET restrictions, Securitize’s events follow the listing exchange’s halt and resumption and can arrive with a short delay. They are best effort: halts and suspensions are published when known to Securitize, and short limit-up/limit-down pauses are not. Your obligation to stop trading alongside the exchange stays with you and your own market data; use these events for confirmation and audit, and marketStatus for the computed answer at any moment. Market-wide halts arrive as one UNDERLYING_MARKET restriction per asset you hold, all with the same reasonCode MARKET_WIDE_CIRCUIT_BREAKER, and are lifted together.

Get started

Guides

Concepts

Help

API reference

The effective status

Restrictions as events

What to do when one arrives

Underlying market signals