Developer documentation
Choose the right DALP developer guide for API integration, CLI automation, platform setup, compliance configuration, asset operations, data feeds, and operator runbooks.
The developer guides route builders, platform administrators, and identity reviewers to the DALP surface they need. Pick a guide family below to reach the right starting point: wiring a new integration, scripting tenant tasks, configuring identity controls, or diagnosing a live issue.
Choose the guide family that matches the work in front of you. Use API integration for application traffic, CLI for scripted tasks, platform configuration for administrator work, compliance for KYC and provider controls, asset guides for issuance and servicing, feeds for signed values, and operations for production health.
DALP owns the API contracts, CLI behaviour, platform setup flows, and documented control surfaces here. Your organisation owns the business rules, administrator assignments, wallet approvals, issuer decisions, which compliance providers you connect, which feed signers you use, and which approvals you require through those surfaces.
These guides cover supported DALP integration work. They do not define legal policy, custody policy, SLA commitments, non-EVM chains, bridge operations, privacy posture, or regulator-specific operating procedures. Treat those as organisation-specific controls unless a detail page states the DALP behaviour explicitly.
What DALP covers
The API and CLI can create users, change administrator roles, configure compliance, deploy or service assets, submit feed updates, submit transactions, and inspect platform state when the caller has the required permissions. DALP sets the contracts, command behaviour, and permission rules, and returns a signed record for each call. Your organisation decides which calls are allowed, who may approve them, and which controls must exist around them.
| Area | DALP defines | Your organisation defines |
|---|---|---|
| Access | API contracts, CLI commands, authentication flows, and permission checks | Which users, service accounts, and operators receive credentials or roles |
| Asset operations | Supported asset creation, servicing, compliance, feed, and transaction workflows | Issuer decisions, approval chains, wallet approvals, and production operating policy |
| Evidence | Indexed state, request logs, events, status checks, and operational read models | Retention policy, regulator-specific reporting, control testing, and escalation procedures |
| Exclusions | Documented platform behaviour only | Legal policy, custody policy, SLA commitments, bridge operations, privacy posture, and non-EVM deployment decisions |
Pick the right path
| If you need to... | Start here | Then read |
|---|---|---|
| Build a programmatic integration | API getting started | API reference guide for the OpenAPI explorer and generated clients |
| Understand organization and system scope | Organization and system scope | Platform overview for tenant setup context |
| Receive lifecycle events | Events catalogue | Webhook delivery, lifecycle states, payload schemas, and audit evidence |
| Automate DALP from scripts or agents | CLI overview | Scripting and automation |
| Prepare a new tenant or administrator model | Platform overview | Admin operating model and first admin setup |
| Connect identity, KYC, or compliance workflows | Choose a KYC issuance path | Onboard a compliance provider |
| Create and service tokenized assets | Create asset | Mint assets |
| Operate prices, NAVs, or signed feed updates | Feeds overview | Submit updates |
| Investigate production operations | Transaction tracking | Blockchain monitoring, system upgrades, and balance reconciliation |
| Follow a complete asset-class walkthrough | Runbooks | The bond, deposit, equity, fund, and stablecoin runbooks below |
Integration model
DALP exposes four developer-facing surfaces:
- The API is the primary surface for applications, backend services, and audit workflows. Call it to create users, deploy assets, manage compliance, submit transactions, or read indexed platform state.
- The API reference guide documents the OpenAPI explorer served at
/api/v2on your DALP host. Use it to inspect route groups, request schemas, response shapes, and the versioned spec before generating clients or copying endpoint examples. - The token events reference is the asynchronous lifecycle-event contract. Use it when downstream systems need signed webhook deliveries, reconciliation inputs, monitoring signals, or audit records after DALP activity happens.
- The CLI is the operator and scripting surface for local work, CI jobs, and AI agent workflows. Run the CLI when a human or scripted process needs a command-line control plane.
Most live integrations combine all three surfaces. The API handles application traffic. Events carry asynchronous records and reconciliation signals. The CLI covers state queries and repeatable scripted tasks. Check the detail pages to confirm prerequisites, permissions, side effects, and errors before you run a workflow in production.
CLI
The CLI is the operator and scripting surface. Use it for local development, CI automation, and agent-driven workflows.
Install the CLI and authenticate against your deployment.
Complete reference for all CLI commands across every domain. Look up flags, required arguments, and output formats before scripting.
Use the CLI in shell scripts, CI/CD pipelines, and batch operations. The guide covers output parsing, exit codes, and credential management for automated contexts.
Connect the CLI to approved local agents. Covers shell execution, the MCP integration, and generated agent skills.
API integration
The Platform API is the primary surface for application traffic, audit workflows, and backend services. The cards below cover authentication, the OpenAPI explorer, events, error handling, and key resource APIs.
Create your first API key and configure the TypeScript client.
Locate the OpenAPI explorer on your DALP deployment, fetch the spec for code generation, and use the API tooling safely.
Lifecycle events are the asynchronous record for webhook delivery, reconciliation signals, and audit evidence. The platform signs each event payload so downstream systems can verify authenticity.
Understand how DALP separates organisation-scoped assets from system-scoped services.
Visual flowcharts covering the full token lifecycle: from initial creation through minting and transfers to burns.
Query holder balances and execute governed transfer workflows. The platform enforces compliance checks before approving each transfer.
Store named wallet recipients for safer transfer and servicing operations.
Handle errors correctly: each code maps to a specific caller response, a retry decision, and an escalation path.
Configure pushed event delivery. Covers payload privacy controls, retry policy, and the HMAC signing scheme used for audit proofs.
List paymasters, check funding levels, manage sponsorship policies, and rotate signer keys. Paymasters cover gas costs for account-abstracted transactions so integrators don't pass gas fees to end users.
Install the TypeScript SDK and choose the right client setup for your integration.
Query request volume, latency, error rates, request logs, and live API activity. Use these metrics to detect integration issues before they affect users.
Attach and retrieve token document metadata through the API. The platform validates each document reference against the token record.
Integrate XvP settlement: preparation, execution, and status polling through finality.
Check smart-wallet approval requirements before executing governed calls. The platform returns the required signer count and current approval state.
Map DALP error codes to operator steps, retry handling, and support evidence.
Format asset amounts correctly using decimal configuration. Incorrect decimal handling causes silent precision loss in transfer amounts.
Platform setup
These guides cover tenant initialization, administrator role assignment, and the operating model for those who manage platform access.
API-based platform setup and administrator role management. Start here before provisioning users or deploying assets.
Initialize your deployment with the first administrator account.
Grant administrative permissions to users in your organisation. The platform enforces role separation between tenant-level and asset administrators.
Plan administrator responsibilities, role assignment, and operational ownership. Use this guide before provisioning: it defines which administrator types your organisation needs, what each role can approve, and how to separate duties between platform and asset administration.
Grant or revoke platform administrator roles. Each change is recorded in the audit log with a timestamp and actor identity.
User management
Create users, then register them in the identity registry before issuing KYC claims.
Create users with automatic wallet provisioning and on-chain registration. Each user receives a managed smart wallet on creation.
Register users in the identity registry so the platform can enforce KYC controls. Registration is required before the platform accepts KYC claims for a user.
Compliance
These guides cover KYC issuance paths, trusted issuer configuration, identity verification modules, and compliance provider onboarding.
Decide whether to issue manual KYC claims or connect a compliance provider.
Configure entities authorized to issue verifications.
Issue KYC verifications to registered users. The platform records each verification against the user's on-chain identity.
Configure identity verification compliance modules.
Add a compliance provider, provision its issuer EOA, and configure webhooks. The provider then issues claims directly to user identities.
Configure collateral ratios and backing requirements.
Asset creation
Asset servicing
After deployment, use these guides to manage roles, mint units, handle forced transfers, and pause assets when required.
Grant or revoke administrator roles for specific assets.
Issue new units to investors. The platform verifies compliance status before crediting tokens to the recipient wallet.
Administratively move assets between wallets for compliance or recovery. Requires the asset-level agent role.
Enable or disable all transfers for an asset.
Feeds
On-chain data feeds deliver signed values used for price reporting, NAV tracking, and oracle data. Each feed is deployed as a contract; integrators submit cryptographically signed updates and read values through the Platform API.
On-chain data feeds for price reporting, NAV tracking, and oracle data.
Deploy issuer-signed feeds, aggregator adapters, and register external feeds.
Submit EIP-712 typed feed updates with nonce management. The platform rejects updates with invalid signatures or stale nonces.
Query latest values, historical rounds, and check feed staleness.
Operations
These runbooks cover production health: transaction status, chain monitoring, indexer state, system upgrades, workflow recovery, and balance reconciliation.
Check transaction status after timeout errors.
Monitor chain RPC and indexer health from the API or CLI. The platform exposes health endpoints for both the node and the Ledger Index.
Review upgrade status and run controlled system upgrades.
Recover blocked workflow engine workflows and clean stale deployments. Use this guide when a workflow stalls after a partial transaction.
Compare on-chain state with your internal records.
Runbooks
The top-level runbook shelf is the authoritative index for DALP runbooks. It keeps developer guides, identity walkthroughs, and API-led scenario guides near the integration material they depend on.
Use these pages when the task starts from an API, CLI, script, or integration test. Use the user-guide runbook shelf when the same scenario needs Console steps. The equity tokenization walkthrough appears in both locations because the API and Console versions serve different readers.
API-led walkthrough for multi-organisation equity tokenization. The scenario runs from user creation through KYC, asset deployment, and the first investor mint.
Create debt instruments with coupon schedules and maturity dates.
Issue deposit certificates with interest accrual.
Deploy equity tokens with dividend distribution. Includes collateral and compliance configuration steps.
Launch fund tokens with NAV tracking. The runbook covers feed setup for NAV updates and subscription workflows.
Create collateral-backed stablecoins.
Add collateral requirements using the Compliance Module API. Configure backing ratios before the asset accepts subscriptions.