Improved

Deprecation notices now rendered in API reference descriptions

Deprecated operations, parameters, and schema properties now carry a standardized deprecation notice in their published description, generated from the deprecation metadata (reason, and migration link when one exists). Hand-written deprecation sentences have been removed from those descriptions so each notice appears once, consistently formatted.

  • easy_to_borrow on the asset schema now shows a generated notice pointing to borrow_status.
  • original_amount on the funding wallet transfer schema points to total_amount (sunset 2026-12-21).
  • client_id on the tokenization mint callback and redeem request schemas points to client_external_account_id (sunset 2026-10-15).
  • account and issuer_account on the tokenization request schema point to client_account_id and client_external_account_id (sunset 2026-10-15).
  • ISIN on the ACATS asset schema and the deprecated field note on the create transfer request are covered by the same generated notices.

No request or response shapes change; this affects documentation rendering only.

Broker API

  • GET /v1/assets
  • GET /v1/assets/{symbol_or_asset_id}
  • GET /v1beta1/acats/{account_id}/{acats_id}/assets
  • POST /v1/accounts/{account_id}/transfers
  • GET /v1beta/accounts/{account_id}/funding_wallet/transfers
  • GET /v1beta/accounts/{account_id}/funding_wallet/transfers/{transfer_id}
  • POST /v1beta/accounts/{account_id}/funding_wallet/withdrawal
  • GET /v1/accounts/{account_id}/tokenization/requests
  • GET /v1/accounts/{account_id}/tokenization/requests/{tokenization_request_id}
  • GET /v1/accounts/{account_id}/tokenization/requests:by_client_request_id
  • GET /v1/accounts/{account_id}/tokenization/requests:by_issuer_request_id
  • POST /v1/accounts/{account_id}/tokenization/callback/mint
  • POST /v1/accounts/{account_id}/tokenization/callback/redeem

Trading API

  • GET /v2/assets
  • GET /v2/assets/{symbol_or_asset_id}
  • GET /v2/tokenization/requests
  • GET /v2/tokenization/requests/{tokenization_request_id}
  • GET /v2/tokenization/requests:by_client_request_id