Skip to main content

Tokenization API Documentation

This is the documentation of the Apex partner API: the integration API through which your systems tokenize real-world assets, run their markets and serve your investors.

Overview​

The platform represents real-world assets as on-chain tokens. Through the partner API your client:

  • Operates the offering (/v2/admin/**): nodes and their contract setups, tokens and their lifecycle (listing, rent, burn, OTC and secondary-market opening), KYC tokens, groups and per-token rules, fees, currency tokens, categories, oracles, ownership changes and analytics.
  • Serves investors (/v2/users/**): onboards and migrates users, manages their wallets, and lets them buy, sell, trade over the counter, list on the secondary market, claim rent and withdraw.
  • Reads chain reference data (/v2/chains, /v2/networks, /v2/gas-sponsor-wallets, /v2/blockchain/gas-fee) and distribution data (/v2/distributions/**).

Key Features​

  • Asset tokenization: deploy contract setups and issue tokens for real-world assets on the network you choose.
  • Token lifecycle: list, delist, rent, burn, retokenize, open to OTC and to the secondary market.
  • KYC and compliance: KYC tokens per network, groups, whitelists, blacklists and distribution lists.
  • Multi-wallet investors: a user can hold several wallets; every wallet-bound operation names the wallet_id and network_id it runs on.
  • Exact amounts: prices, fees and balances travel as decimal strings. See Amounts and Percentages.
  • Asynchronous on-chain work: on-chain operations are accepted immediately and settle in the background; you follow them by polling their transaction.
  • Per-client guards: permissions, IP allow-list, rate limits, monthly usage quota and optional mTLS client certificates.

Authentication​

The API uses OAuth 2.0 bearer tokens.

  1. The platform operator provisions an API client for you (see Create Client).
  2. Exchange your client_id / client_secret for an access token with the client_credentials grant (or a supervisor's username / password with the password grant) via Create a Token.
  3. Send the access token on every call:
Authorization: Bearer <access_token>

A client has one live access token at a time: requesting a new token invalidates the previous one. Refresh tokens are single-use. Errors follow one format.

API Endpoints​

Test Environment​

https://test-integration-api.tokenizationtr.com

Production Environment​

https://integration-api.tokenizationtr.com

Postman Collection​

The Postman collection contains every endpoint of the partner API with example bodies and descriptions.

📥 Download Postman Collection

Instructions:

  1. Download the collection and import it into Postman.
  2. Import the environment for the platform you call:
  3. Fill in clientId and clientSecret in the environment (and username / password if you use the password grant).
  4. Run Authentication → Get Token (Client Credentials) or Get Token (Password). The request stores token and refreshToken in the environment; every other request uses token automatically.
  5. Path variables and ids are left empty in the collection: fill them in from your own data.