Token conversion authorizations

A convertible DALP token can be authorized to convert into one or more target tokens. DALP exposes that authorization as a pair of read endpoints. Together they answer two questions for any token: which target tokens it can convert into, and which source tokens can convert into it.

Use this reference to confirm a conversion route before initiating a conversion, or to reconcile the convertible side of an instrument with its target side. Both endpoints are read-only. They report indexed authorization state and never create, change, or revoke a route.

Two directions of the same authorization

A conversion authorization is a directed link between a source token and a target token. The two endpoints read the same authorization from opposite ends:

Call converts-to with the source token in the path to list its targets. Call converted-from with the target token in the path to list its sources. Both responses use the standard DALP paginated list shape.

List target tokens (converts-to)

curl --globoff "$DAPI_URL/api/v2/tokens/0x1111111111111111111111111111111111111111/conversion/converts-to?page[limit]=50&sort=-authorizedAt" \
  -H "X-Api-Key: $DALP_API_TOKEN"

{
  "data": [
    {
      "targetTokenAddress": "0x2222222222222222222222222222222222222222",
      "conversionFeatureAddress": "0x3333333333333333333333333333333333333333",
      "minterFeatureAddress": "0x4444444444444444444444444444444444444444",
      "isAuthorized": true,
      "authorizedAt": "2026-06-06T12:00:00.000Z",
      "revokedAt": null,
      "updatedAt": "2026-06-06T12:00:00.000Z"
    }
  ],
  "meta": {
    "total": 1,
    "facets": {}
  },
  "links": {
    "self": "/v2/tokens/0x1111111111111111111111111111111111111111/conversion/converts-to?sort=-authorizedAt&page%5Boffset%5D=0&page%5Blimit%5D=50"
  }
}

List source tokens (converted-from)

curl --globoff "$DAPI_URL/api/v2/tokens/0x2222222222222222222222222222222222222222/conversion/converted-from?page[limit]=50&sort=-authorizedAt" \
  -H "X-Api-Key: $DALP_API_TOKEN"

{
  "data": [
    {
      "sourceTokenAddress": "0x1111111111111111111111111111111111111111",
      "conversionFeatureAddress": "0x3333333333333333333333333333333333333333",
      "minterFeatureAddress": "0x4444444444444444444444444444444444444444",
      "isAuthorized": true,
      "authorizedAt": "2026-06-06T12:00:00.000Z",
      "revokedAt": null,
      "updatedAt": "2026-06-06T12:00:00.000Z"
    }
  ],
  "meta": {
    "total": 1,
    "facets": {}
  },
  "links": {
    "self": "/v2/tokens/0x2222222222222222222222222222222222222222/conversion/converted-from?sort=-authorizedAt&page%5Boffset%5D=0&page%5Blimit%5D=50"
  }
}

Fields

The two endpoints return the same edge fields. They differ only in which token address is the counterparty: converts-to returns targetTokenAddress, and converted-from returns sourceTokenAddress.

Query controls

Both endpoints use the standard JSON:API query pattern for pagination, sorting, filtering, and facets.

These endpoints do not support global text search.

Behaviour

• A token with no authorized or revoked conversion routes returns an empty data array with total set to 0. The endpoint does not infer routes from another token or tenant.
• A revoked route is still returned, with isAuthorized set to false and revokedAt populated. Filter on isAuthorized when you want only the active routes.
• The endpoints read indexed authorization state. The read does not make a live contract call, authorize a new route, revoke a route, or execute a conversion.
• Results are scoped to the tokens your organization can see. A token outside that scope returns an empty paginated response rather than an error.

SDK and CLI

The same reads are available through the SDK and CLI.

const targets = await client.token.convertsTo({
  params: { tokenAddress: "0x1111111111111111111111111111111111111111" },
  query: { filter: { isAuthorized: true } },
});

const sources = await client.token.convertedFrom({
  params: { tokenAddress: "0x2222222222222222222222222222222222222222" },
  query: { filter: { isAuthorized: true } },
});

dalp tokens converts-to 0x1111111111111111111111111111111111111111
dalp tokens converted-from 0x2222222222222222222222222222222222222222

Related

• Token conversion records to reconcile completed conversions across the source and target tokens.
• Token conversion triggers to read the triggers that drive a conversion.
• Conversion token feature for how the convertible instrument is configured.
• Token lifecycle API for the wider token read surface.
• API reference for the generated OpenAPI contract and a typed client for these endpoints.