Tokenization API and digital asset platform API integration
Choose the right DALP tokenization API and digital asset platform API page for authentication, OpenAPI client generation, request headers, errors, webhooks, EVM token lifecycle workflows, token data, durable workflow recovery, smart wallets, and XvP settlement flows.
DALP tokenization API and digital asset platform API docs are grouped by the job you are doing and by documentation type. Developers use these pages to authenticate with the public API, generate clients from the OpenAPI contract, integrate configured EVM token lifecycle and asset data workflows, handle webhooks and events, and add production controls around errors, headers, monitoring, and recovery. The tokenization surfaces in these pages are EVM-only.
If you are new to DALP APIs, read Getting started first, then generate or configure a typed client from SDK integration. If you already know the integration surface, use the tables below to jump straight to the tokenization endpoint family, account abstraction surface, webhook guide, error model, or operational guide you need.
Public API paths
DALP exposes the current REST API under /api/v2 and serves its OpenAPI contract at /api/v2/spec.json. Use /api/v2 for new tokenization API and digital asset platform API integrations. Bare /api redirects to /api/v2. Use /api/v1 and /api/v1/spec.json only when you maintain an existing v1 client.
Token and asset operations use versioned paths such as POST /api/v2/tokens, PATCH /api/v2/tokens/{tokenAddress}/metadata, GET /api/v2/tokens/{tokenAddress}/events, and GET /api/v2/system/stats/portfolio-breakdowns. See API reference for the full route contract before adding request bodies, headers, or generated client code.
One-view route map
The route map shows the usual reading order for tokenization API work. Authentication and client setup come first, the OpenAPI contract anchors implementation, and the domain pages narrow the endpoint family before you add production controls.
Start here
| Type | If you need to | Read | Outcome |
|---|---|---|---|
| How-to | Create an API key and make the first authenticated call | Getting started | Configure API key authentication and a generated TypeScript client. |
| How-to | Choose SDK generation and client conventions | SDK integration | Generate and organise a typed client around the OpenAPI contract. |
| Reference | Generate clients or inspect endpoint contracts | API reference | Use the OpenAPI explorer and specification contract. |
| How-to | Decide how API calls should behave in production | Request headers and error handling | Set participant, wallet, idempotency, transaction-speed, and recovery behaviour before automation. |
Pick the integration pattern
Choose the integration shape before you pick an endpoint. Most DALP tokenization API integrations combine a typed API client for commands, token and asset reads for reconciliation, event or webhook flows for downstream systems, and operational health checks for runbooks.
Treat this index as a route map, not as the endpoint contract. The endpoint pages and OpenAPI reference remain the source for request bodies, response shapes, and supported headers.
| Integration job | Best starting point | Use this when |
|---|---|---|
| Backend service or customer application integration | SDK integration and API reference | You need a typed client, API-key authentication, and a stable contract for application code. |
| Off-chain ledger, cap table, analytics, or audit sync | Operational integration patterns | You need event replay, holder reconciliation, transaction-status checks, and idempotent reads. |
| Event-driven partner or provider workflows | Webhook endpoints | You need DALP to receive external provider callbacks or reconcile provider event delivery. |
| Production support and incident response | API monitoring and blockchain monitoring | You need health, readiness, indexer, RPC, finality, and snapshot-stream signals for operations. |
Core integration model
| Type | If you need to | Read | Outcome |
|---|---|---|---|
| Reference | Configure shared headers for acting participants, execution wallets, idempotency, and transaction speed | Request headers | Send headers only on routes that support them, with the right fallback behaviour. |
| Reference | Discover organisations, systems, networks, implementations, and contract factories | System directory API | Resolve the platform directory data needed before calling scoped API surfaces. |
| Concept | Scope integrations across organisations and systems | Organisation and system scope | Keep API keys, organisations, systems, and permission boundaries aligned. |
| Concept | Reuse operational patterns across API integrations | Operational integration patterns | Plan retries, idempotency, transaction tracking, and production handoffs. |
Tokenization API surfaces
| Type | If you need to | Read | Outcome |
|---|---|---|---|
| Reference | Manage token lifecycle operations | Token lifecycle | Create assets, change supply, manage holders, documents, metadata, permits, and decimals. |
| Reference | Update mutable token metadata | Token metadata | Set or remove issuer-defined metadata fields and inspect metadata update behaviour. |
| Reference | Register deployed EVM tokens | External tokens | Register and list already deployed EVM tokens inside DALP. |
| Reference | Attach and retrieve token documents | Token documents | Manage document links and metadata for asset records. |
| Reference | Work with token holders and transfers | Token holders and transfers | Inspect holder balances and transfer-related API surfaces. |
| Reference | Read indexed token events | Token events | Query token activity, wallet-scoped event history, facets, pagination, and dapp table behaviour. |
| Reference | Resolve asset pricing and statistics | Token price resolution, Exchange rates, Token volume statistics, Yield coverage statistics, Portfolio statistics, and Asset decimals | Read pricing, FX rates, volume, yield, portfolio, and decimal precision surfaces. |
| Reference | Integrate XvP settlement flows | XvP settlement flows | Integrate hold, release, settlement, and cancellation workflows for XvP settlement. |
Wallets/account abstraction
| Type | If you need to | Read | Outcome |
|---|---|---|---|
| Concept | Discover smart accounts and approvals | Smart wallets, Smart wallet approvals, and Smart wallet thresholds | Discover wallets, review approval requirements, and inspect threshold settings. |
| Reference | Recover wallet identity links | Identity recovery | Inspect identity recovery surfaces for smart-account integrations. |
| Reference | Read native account balances | Account native balances | Read native asset balances for accounts. |
| Reference | Discover account abstraction network support | Account abstraction transaction relay | Discover the active chain and ERC-4337 EntryPoint support. |
| Reference | Operate sponsored gas settings | Gas sponsorship paymasters | Inspect paymaster balances, deposits, sponsorship configuration, and signer keys. |
Compliance APIs
| Type | If you need to | Read | Outcome |
|---|---|---|---|
| Reference | Reuse compliance templates | Compliance templates | Apply reusable compliance rules to asset and transfer workflows. |
| Reference | Configure module-backed transfer controls | Compliance modules | Configure compliance modules that enforce transfer controls. |
| Reference | Work with address-book contacts | Address book contacts | Review contact data that supports allowlist and counterparty workflows. |
| How-to | Upload KYC documents | KYC document uploads | Send KYC evidence files through DAPI so DALP can validate, encrypt, store, list, and download them on a KYC version. |
Reporting, monitoring, and recovery
| Type | If you need to | Read | Outcome |
|---|---|---|---|
| Concept | Monitor API operations | API monitoring | Track health, latency, and operational signals around API integrations. |
| Reference | Map reporting and audit evidence surfaces | Reporting and audit access | Choose holder, event, action, export, webhook, and transaction evidence for reporting. |
| Reference | Plan operator recovery for blocked durable workflow state | workflow engine recovery | Check when recovery actions are appropriate before changing workflow state. |
| Reference | Call workflow engine operator routes | workflow engine operator API | Inspect route bodies, success payloads, component statuses, and retry-blocked behaviour. |
Webhooks/integrations
| Type | If you need to | Read | Outcome |
|---|---|---|---|
| Reference | Receive platform events | Events catalogue | Configure webhook destinations, then use the event reference for lifecycle states and payload schemas. |
Error/API reference
| Type | If you need to | Read | Outcome |
|---|---|---|---|
| How-to | Handle API and OpenAPI errors | Error handling | Distinguish request validation, platform errors, and error-code recovery paths. |
| Reference | Look up API error identifiers | API error reference | Match returned API error identifiers to status, retry behaviour, and recovery. |
| Reference | Look up smart contract error codes | Smart contract error reference | Decode contract revert codes returned through API error responses. |
Example reading paths
| Scenario | Read in this order | Why this path works |
|---|---|---|
| First API integration | Getting started, SDK integration, API reference | You authenticate first, generate a client, then confirm request and response shapes against the contract. |
| KYC evidence upload | Request headers, KYC document uploads, error handling | You set acting context before the upload, then handle validation, storage, listing, download, and retry behaviour. |
| Production reconciliation | Operational integration patterns, Token events, Reporting and audit access, API monitoring | You pair reads and event history with audit evidence and health signals before automation depends on them. |
| XvP settlement integration | XvP settlement flows, Request headers, error handling, blockchain monitoring | You implement the settlement workflow, then add participant context, recovery rules, and chain operational checks. |
Keep the navigation narrow
Use this index for routing. Endpoint reference pages, generated OpenAPI pages, and workflow guides remain the source for implementation details.
For mutation pages, check request headers, error handling, and idempotency first. Review monitoring and recovery notes before production automation.