Errors overview
Index of DALP's error catalogs and handling guidance. Map an error to the right reference page, find its domain, and choose the next action.
This section catalogs the errors your integration can encounter when calling DALP. Two reference pages list every code. A handling guide covers retry policy, idempotency behavior, and when to escalate to support. Use this page to reach the right reference for the kind of error you have.
When to read what
| You have... | Read |
|---|---|
| An error code returned by a Platform API route (auth, validation, upstream, rate-limit, system) | Platform API error reference |
| An error revert from a smart contract (compliance check, settlement, system, OpenZeppelin) | Smart contract error code reference |
| A general question about retry, idempotency, or error surface design | Error handling |
The reference pages are large because they cover every code DALP can return. Use this page to jump to the relevant section instead of scrolling.
Smart contract error code domains
The smart contract error code reference groups codes by the operation that triggered them. Use the anchor link to jump to the relevant domain:
- Compliance and token operations: identity verification, country restrictions, allowlist or blocklist rejections, transfer approvals, supply-cap or collateral check failures, and other compliance-module failures.
- Settlement and XvP: XvP settlement state transitions, hashlock or window failures, approval errors, and cancellation rejections.
- Airdrop and distribution: distribution-state rejections from the airdrop addon and its claim-tracker variants.
- System and infrastructure: system contract, directory, registry, and factory rejects, plus access-manager failures.
- Internal (OpenZeppelin and low-level): OpenZeppelin selector-revert payloads (e.g.,
Ownable,AccessControl,Pausable) and other low-level reverts surfaced when no higher-level cause is available.
The reference page includes a summary table of counts per domain.
Platform API error domains
The Platform API error reference lists every Platform API error code. Use the anchor links to jump to the relevant section in the long reference. The Platform API reference groups entries by category. Each entry also shows its HTTP status:
- Authentication and authorisation rejections (
401,403). - Request validation rejections (
400,422). - Rate-limit and quota rejections (
429). - Upstream and external integration failures (
502,503,504). - System and platform rejections (
500).
Every code has a fixed shape: id, category, status, retryable, message, why, and fix. Branch your integration logic on the stable id value in the public error object, not on the message text.
Handling guidance
The error-handling guide covers the cross-cutting concerns. Use it to understand retry policy, including which errors are retryable, which carry an idempotency contract, and what backoff shape to apply. It also covers idempotency key usage with mutation endpoints, status polling for asynchronous blockchain mutations, error-response shape across REST and RPC routes, and which fields to include when escalating an unresolved error.
Read the handling guide before integrating against the references. The references describe what each code means. The handling guide describes what your integration does about it.
Read next
- Platform API error reference
- Smart contract error code reference
- Error handling
- Transaction tracking for status polling against async blockchain mutations.