Developer guides

The developer guides are for teams that build, automate, and operate DALP integrations. Integrating developers use them for API and CLI work. Platform administrators use them for tenant setup, access, and asset operations. Compliance reviewers use them to find the controls, evidence paths, and handoffs that matter before production.

Choose the guide family that matches the surface you need to operate. Start with API integration for application traffic, CLI for scripted operations, platform setup for tenant and administrator work, compliance for identity 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 in this section. Your organisation owns the business policy, administrator assignments, wallet approvals, issuer decisions, compliance provider configuration, feed signers, and runbook approvals that you apply through those surfaces.

These guides cover supported DALP integration work. They do not define legal policy, custody policy, SLA commitments, non-EVM deployment support, 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 defines the contracts, command behaviour, permission checks, and returned evidence. Organisation policy decides when those actions are allowed, who may approve them, and which operating controls must exist around them.

Pick the right path

Integration model

DALP exposes four developer-facing surfaces:

• The API is the integration surface for applications, backend services, and evidence workflows. Call the API to create users, deploy assets, manage compliance, submit transactions, or read indexed platform state.
• The API reference guide documents the per-deployment OpenAPI explorer served at /api/v2 on your DALP host. Use it to inspect route groups, request schemas, response shapes, and the versioned specification before generating clients or copying endpoint examples.
• The events catalogue under /docs/events is the asynchronous lifecycle-event contract. Use it when downstream systems need signed webhook deliveries, reconciliation inputs, monitoring signals, or audit evidence after DALP activity happens.
• The CLI is the operator and automation surface for local work, CI jobs, scripted administration, and AI agent workflows. Run the CLI when a human or automation process needs a command-line control plane.

Most production integrations combine the API, events, and CLI. Use the API for application traffic, events for asynchronous evidence and reconciliation, and the CLI for setup, inspection, and repeatable operational tasks. Use the detail pages to confirm prerequisites, permissions, side effects, errors, and audit evidence before you run a workflow in production.

CLI

API integration

Platform setup

User management

Compliance

Asset creation

Asset servicing

Feeds

Operations

Runbooks

The top-level runbook shelf is the authoritative index for DALP runbooks. This shelf keeps developer runbooks, compliance configuration runbooks, and API-led scenario walkthroughs near the integration material they depend on.

Use these pages when the operation 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 shelves because the API and UI versions serve different readers.