The DALP Platform API lets integrations manage assets, participants, compliance, and settlement. Call it directly, use the TypeScript SDK, or run CLI commands. An integration sends an API key in the X-Api-Key header, and Authentication and API keys covers creating one. These pages cover authentication, retries, errors, and event handling. The API explorer supplies request and response schemas for each route.
The asset issuance routes create a composable token: one token contract on an EVM network, composed from extensions and token features.
Public API paths
DALP serves the current REST API at /api/v2, with its OpenAPI contract at /api/v2/spec.json. Point new integrations at /api/v2. Only the bare /api root redirects there. A path under /api with no version segment, such as /api/tokens, is served as /api/v1/tokens, so always write /api/v2 in the base URL. Use /api/v1 and /api/v1/spec.json only for an existing v1 client. Browse the full contract and generate a client from the v2 API explorer, or the v1 API explorer for the legacy surface. The explorers read the contract. They do not send requests, so test a call against your own deployment with the CLI or your generated client.
Token, wallet, compliance, settlement, trading-venue, offering, observability, and administration endpoints are documented in full only in that generated contract. The guides walk through selected workflows with example calls and responses, and the explorer is the source of truth for every field, header, and status code.