Unified API
The Unified API provides type-safe programmatic access to all digital asset lifecycle operations. With automatic OpenAPI generation, the API combines type safety, comprehensive documentation, and multi-layer security including wallet verification for blockchain transactions.
Overview
The Unified API exposes all DALP platform capabilities through a type-safe, documented interface. Integration engineers connect existing systems to asset lifecycle operations without understanding blockchain implementation details. Every procedure validates inputs, enforces permissions, and produces consistent responses.
Enterprise integrations demand predictable interfaces with comprehensive documentation. The Unified API delivers OpenAPI 3.1 specifications generated directly from procedure definitions, ensuring documentation stays synchronized with implementation. Interactive exploration through Swagger UI at /api enables rapid integration development.
Procedure namespaces
Procedures organize by domain rather than REST resource conventions. This organization reflects how operators think about platform capabilities.
| Namespace | Purpose | Example procedures |
|---|---|---|
token | Asset lifecycle operations | Create, mint, burn, transfer, pause |
user | User management | List users, assign roles, manage permissions |
account | Wallet operations | Generate address, check balance, sign transactions |
contact | Investor relationships | Register investor, record verifications |
asset | Asset metadata | Update documents, configure compliance rules |
system | Platform administration | Health checks, configuration, audit logs |
API design principles
The API follows consistent design patterns across all procedures:
Contract-first development: Schema definitions validate all inputs before business logic executes. Changes to schemas immediately surface as errors in consuming code.
Automatic documentation: OpenAPI 3.1 specifications generate from procedure definitions. No manual synchronization required between implementation and documentation.
Consistent serialization: Complex types like large numbers, dates, and blockchain-specific values serialize correctly across the wire.
Middleware composition: Cross-cutting concerns like authentication, rate limiting, and audit logging apply consistently across procedure groups.
Interactive documentation
Swagger UI provides interactive API exploration at /api. Developers authenticate, construct requests, and execute procedures directly from documentation. Response schemas display alongside actual responses for validation.
The OpenAPI specification exports for client generation in any language. Generated clients benefit from type safety matching the server implementation.
Meta-transaction support
The API supports meta-transactions through the underlying ERC-2771 integration. Callers can submit signed transaction payloads without holding native tokens for gas. A configured relayer service sponsors transaction costs while the user's signature authorizes the operation.
This capability enables:
- Simplified user experience - Investors interact with tokens without managing cryptocurrency for fees
- Sponsored operations - Issuers cover transaction costs for their investors
- Gasless workflows - Automated systems execute transactions without native token management
Meta-transactions work transparently through the API—callers submit signed payloads, and the platform handles relay coordination.
Enterprise messaging integration
The API supports integration with enterprise financial messaging systems for institutions requiring connectivity to existing infrastructure:
- Standards-based messaging - Structured message formats for corporate actions, settlement instructions, and asset servicing
- Automated reconciliation - Outbound notifications for completed transactions enable downstream system updates
- Audit trail synchronization - Transaction events can trigger messages to compliance and reporting systems
These integrations connect blockchain-native operations to traditional financial infrastructure, enabling hybrid workflows where DALP handles tokenization while existing systems manage related processes.
Error handling
Errors return structured responses with consistent formats across all procedures. Error responses include machine-readable codes alongside human-readable messages.
| Category | HTTP status | Action |
|---|---|---|
| Validation errors | 400 | Fix request payload |
| Authentication failures | 401 | Reauthenticate |
| Authorization denied | 403 | Check role permissions |
| Resource not found | 404 | Verify identifier |
| Rate limited | 429 | Retry after delay |
| Server errors | 500 | Retry with exponential backoff |
Blockchain-specific errors include transaction details: gas estimation failures, revert reasons, and nonce conflicts surface as structured error responses.
See also
- Authentication for identity and API key management
- Security for wallet verification and rate limiting
- Asset Console for web interface
- DALP Execution Engine for operation coordination
- API integration guide for implementation details
Asset Console
The Asset Console provides a comprehensive web interface for digital asset lifecycle management. Built with enterprise authentication, full white-labeling, and multi-language support, the console adapts to institutional requirements while maintaining consistent security standards.
Overview
The infrastructure layer contains the backend services that orchestrate workflows, manage cryptographic keys, sign transactions, index blockchain events, and provide network connectivity. These services are not accessed directly by users -- they operate behind the platform interfaces.