API referenceErrors
Platform API error reference
Complete reference of all Platform API error codes returned by the DALP API, with HTTP status, retryability, and remediation guidance.
DALP returns Platform API error identifiers as stable, machine-readable values in API error responses. Use this page when a Platform API client receives a DALP-#### code and needs to decide whether to fix the request, refresh indexed state, or retry later.
Each error maps to an HTTP status, a retry flag, a public reason, and a recommended recovery step. The TypeScript SDK exposes API failures as DalpApiError, with code, category, retryable, message, why, and fix. Structured responses can also provide id, status, and route-specific data. REST and RPC callers should read these fields from the public error envelope instead of matching on free-text messages.
Retry only when the row marks the error as retryable. For retryable dependency or indexing errors, retry with a short backoff and check the affected resource state before you resubmit a mutating operation. For a non-retryable client, auth, permission, domain, or contract error, change the request, the credentials, the permissions, the token state, or the upstream provider configuration before you try again.
If an error tells you to contact support, include the request id from the API response or the logs. Do not send secrets, raw signatures, private keys, or unredacted identity documents.
On-chain revert codes are documented separately in the error code reference, and the DALP error index lists every id from both pages in one lookup table. Compliance-provider errors may require provider-side checks: Sumsub, Elliptic, Notabene.
How to use this reference
- Match the
idin the error envelope to the table row. - Check the HTTP status and the category to separate request problems from permission, domain, dependency, contract, and operational failures.
- Use
Retryableas the retry gate.Yesmeans the condition may clear after indexing, dependency recovery, workflow completion, or another transient state change.Nomeans the caller must change something first. - Follow the row's suggested fix. For a mutating operation, verify the current resource or transaction state before you retry, so the client does not submit the same operation twice.
Do not parse the human-readable Message, Why, or Suggested Fix columns for program logic. Public copy can become clearer over time. Branch on the stable DALP-#### code together with the retry flag and the HTTP status from the API error envelope.
Contents
- Client request errors: 215 errors.
- Authentication errors: 15 errors.
- Permission errors: 48 errors.
- Domain rule errors: 208 errors.
- Operational errors: 44 errors.
- Dependency errors: 90 errors.
- Contract errors surfaced at the API: 1 error.
- Unclassified errors: 1 error.
Client request errors
| DALP Code | Message | Why | Suggested Fix | Severity | Retryable | HTTP Status |
|---|---|---|---|---|---|---|
| DALP-0001 | The request could not be read. | The request body, query, or headers did not match the published schema for this route. | Check the field names, types, and content type against the route schema, then send the request again. | info | No | 400 |
| DALP-0022 | Resource not found. | The requested resource could not be found. | Check the identifier and retry only if the resource should exist. | info | No | 404 |
| DALP-0023 | Resource already exists. | The request tried to create or register a resource that already exists. | Use the existing resource or choose a unique identifier. | info | No | 409 |
| DALP-0024 | The change conflicts with the current resource state. | Another write already changed this resource, or the resource is already in the requested state. | Read the current resource, resolve the difference, and send the request again. | info | No | 409 |
| DALP-0046 | Reindex request wasn't accepted. | The requested blockchain reindex range, target, or mode was rejected by the Ledger Index reindex admin. | Adjust the reindex request to a supported chain, range, and mode before retrying. | info | No | 400 |
| DALP-0048 | API monitoring log entry was not found. | No API monitoring log entry exists for the requested id in the active organization. | Verify the log entry id and organization, then retry. | info | No | 404 |
| DALP-0054 | Deployment not found. | The requested deployment id is malformed, stale, or does not belong to a deployment the caller may observe. | Refresh deployment state and subscribe using the current deployment id. | info | No | 404 |
| DALP-0061 | XvP hashlock must be a 0x-prefixed hex string. | A cross-chain XvP settlement was created with a hashlock that is not valid hex. | Send a 0x-prefixed hashlock or provide the secret so the API can derive it. | info | No | 400 |
| DALP-0070 | XvP approval was not found. | The caller has not approved the requested XvP settlement or the approval is not indexed. | Approve the settlement first or retry after indexing catches up. | info | No | 404 |
| DALP-0080 | Input validation failed. | The request body or parameters did not match the API contract. | Check the request fields against the API documentation and retry with valid values. | info | No | 422 |
| DALP-0091 | Asset type template not found. | The platform searched for the asset type template by the supplied ID and found no record owned by your organization or available as a system template. | Confirm the ID matches an existing template owned by your organization or a published system template. Re-fetch the list of asset type templates to verify the ID before retrying. | info | No | 404 |
| DALP-0116 | Exchange rate not found. | No active FX feed covers the requested currency pair on the current chain, or the feed exists but has not yet recorded an observed rate. | Check the supported currencies list to confirm the pair is available. If the pair was recently added, retry after the feed publishes its first observation. | info | No | 404 |
| DALP-0125 | Feed with address {feedAddress} not found. | The platform could not find a feed at the given address in the system index. The feed may not have been registered, or the indexer has not yet processed its registration event. | Confirm the feed address is correct and the feed has been registered in the system. If the feed was recently registered, wait for the indexer to catch up and retry. | info | No | 404 |
| DALP-0127 | FeedsDirectory not found for system {feedAddress}. Ensure V3 bootstrap completed and the indexer has caught up. | The platform could not find a FeedsDirectory address for this system in the index. This means the system has not completed its V3 bootstrap, or the indexer has not yet processed the bootstrap event. | Complete the V3 bootstrap for the system and wait for the indexer to process the event before retrying. | info | No | 404 |
| DALP-0175 | Theme payload exceeds supported limits. | One or more fields in the submitted theme configuration exceed the platform's size or structural constraints. This is checked before any data is stored. | Review the violations detail returned with this response and reduce the offending field values to within the stated limits, then resubmit. | info | No | 400 |
| DALP-0227 | Addon factory {factoryAddress} was not found in the indexer. | The platform looked up the addon factory by its on-chain address in the indexer and found no matching record. The factory may not yet be indexed or the address is not registered on this system. | Confirm the factory address is correct and that the indexer has processed the registration transaction. Retry after the indexer catches up. | info | No | 404 |
| DALP-0242 | Topic "{topicId}" not found. | The current organization's topic scheme registry has no topic registered under the name {topicId} on the selected chain. | Verify the topic name, organization, and chain. Create the topic in this organization's topic scheme registry if it is missing. | info | No | 404 |
| DALP-0247 | Module {registryAddress} is not registered in the compliance module registry. | The platform checked the compliance module registry for the given module address and found no matching entry. The module must be registered before it can be uninstalled. | Confirm the module address is correct and that it appears in the system's compliance module registry before calling this operation. | info | No | 404 |
| DALP-0254 | Claim issue failed. | The platform validated the claim topic and data but the claim value failed an auto-claim business rule check specific to the topic type. For example, a boolean auto-claim topic rejected the supplied value. | Review the claim data for the topic named in the request and correct the value to satisfy the topic's validation rules before retrying. | info | No | 422 |
| DALP-0272 | Topic {topicId} is not registered in the topic scheme registry. | The platform searched the registered topic schemes for the requested topic name and found no match. The topic may not exist in this system's claim-topics configuration. | Retrieve the list of registered claim topics via the claim-topics endpoint and use a topic name from that list. | info | No | 404 |
| DALP-0279 | System not found. | The platform resolved the requested system address but found no matching system record in the indexer, and the address does not match this organization's configured system. The system address may be incorrect or belong to a different organization. | Confirm the system address is correct and belongs to your organization. Use the system read endpoint with default to retrieve the active system address for your organization. | info | No | 404 |
| DALP-0283 | Paymaster {paymasterAddress} not found. Confirm the address and check that the indexer has processed it. List available paymasters via GET /v2/system/paymasters. | The platform could not find a paymaster with the given address in the indexed state for this system. The address may be incorrect, or the paymaster may not have been indexed yet. | Confirm the paymaster address is correct and that the indexer has processed the registration transaction. Use GET /v2/system/paymasters to list all paymasters currently indexed for this system. | info | No | 404 |
| DALP-0284 | Paymaster {systemAddress} not found. Confirm the address and check that the indexer has processed it. List available paymasters via GET /v2/system/paymasters. | The platform could not find a paymaster with the given address in the indexed state for this system. The address may be incorrect, or the paymaster registration may not yet be indexed. | Confirm the paymaster address is correct and that the indexer has processed the registration transaction. Use GET /v2/system/paymasters to list all paymasters currently indexed for this system. | info | No | 404 |
| DALP-0285 | Sponsorship paymaster not found with address {paymasterAddress}. | The platform could not find a signer-type paymaster at the given address in the indexed state for this system. The address may be incorrect, the paymaster may belong to a different system, or it may not expose the sponsorship signer type. | Verify the paymaster address belongs to the current system and has the signer paymaster type registered. Use GET /v2/system/paymasters to list available paymasters. | info | No | 404 |
| DALP-0294 | Trusted issuer "{issuerAddress}" not found. | The platform searched the trusted-issuer registry (and its parent chain) in the indexer but found no entry for the given issuer address. The issuer may not have been registered, or the address may be incorrect. | Verify the issuer address is correct and that the issuer has been registered in the system's trusted-issuers registry. Use GET /v2/system/trusted-issuers to list registered issuers. | info | No | 404 |
| DALP-0314 | Token factory for type {factoryAddress} not found. | The platform could not locate a registered token factory for the requested token type, so it cannot proceed with token deployment. | Verify that the token type and optional factory address are correct, and that the system has completed bootstrapping with a factory for that type. | info | No | 404 |
| DALP-0316 | templateId required for token creation. Select an instrument template first. | DALP asset creation requires an instrument template identifier. | Select an instrument template and retry the request. | info | No | 422 |
| DALP-0319 | Access denied - token holder access required. | The requested document has holders visibility, and the authenticated participant holds no role on this token, so the platform cannot serve the download URL. | Request the document with credentials for a participant who holds at least one role on this token, or ask the token administrator to assign an appropriate role. | info | No | 400 |
| DALP-0322 | Document group not found for replacement. | The replaceGroupId supplied in the request does not match any existing document group for this token. No document with that group ID and isLatest=true exists in the platform records. | Confirm the replaceGroupId by listing the token's current documents, then resubmit with a valid group ID. | info | No | 404 |
| DALP-0323 | Document not found. | The document ID supplied does not match any non-deleted document record for this token. The document may have been deleted already or the ID may belong to a different token. | Verify the document ID against the token's active document list and resubmit with a valid ID. | info | No | 404 |
| DALP-0324 | Document type {value} is not valid for asset type {value}. | The requested document type is not permitted for the token's asset type. Each asset type (for example, bond, equity) has a specific set of allowed document types. | Check the list of permitted document types for this token's asset type and resubmit with a compatible document type. | info | No | 400 |
| DALP-0326 | File not found in storage. Upload may have failed. | The platform could not read the uploaded file at the expected storage location. The pre-signed upload may not have completed before the confirm step was called. | Re-upload the file using the pre-signed URL, confirm the upload completed successfully, then call the confirm step again. | info | No | 404 |
| DALP-0327 | Object key is outside the permitted path for this token. | The objectKey in the request does not start with the expected token-documents/:tokenAddress/ prefix, or contains path traversal sequences (.. or //). The platform rejects keys that fall outside the token's storage namespace. | Use the objectKey returned by the upload URL endpoint without modification. Do not alter the path prefix or add traversal sequences. | info | No | 400 |
| DALP-0328 | Token factory not found in the active system. | The requested token factory is not registered in the active system. | Use a token factory returned for the active system. | info | No | 404 |
| DALP-0332 | No yield available to claim. The first yield period has not completed yet. | The platform confirmed from indexed schedule data that fewer than one full interval has elapsed since the yield schedule's start date. No yield periods have completed, so there is nothing to claim. | Wait until at least one full yield interval has elapsed from the schedule start date, then retry the claim. | info | No | 400 |
| DALP-0340 | Token with address {address} not found. | The platform could not find an indexed token at the supplied address within the current system's factory scope. The token may not be deployed, not yet indexed, or belong to a different system. | Verify the token address, confirm the token is deployed and indexed in the current system, then retry. | info | No | 404 |
| DALP-0347 | Token {tokenAddress} is not indexed in the active scope. | Token {tokenAddress} is not indexed in the active tenant and chain scope. | Verify the token address and wait for indexing before retrying. | info | No | 404 |
| DALP-0372 | Missing transfer item. | The platform attempted to process a single-item transfer request but found no transfer items in the transfers array after passing the batch-size check. At least one transfer item is required. | Provide at least one transfer item in the transfers array and retry. | info | No | 422 |
| DALP-0383 | Transaction {transactionHash} not found. | The platform could not locate a transaction with that id in the queue or ownership scope. Transactions belonging to another organization's wallets are reported the same way as genuinely missing ones to prevent enumeration. | Verify the transaction id is correct and belongs to your organization's wallets. If the transaction was recently created, retry after a short delay to allow processing. | info | No | 404 |
| DALP-0417 | KYC profile not found for this request. | The fulfill handler resolved the KYC version linked to the action request but found no KYC profile for the participant who owns that version. The profile row is required to clear the pending-update flag after fulfillment. | Verify the action request ID and that the participant has a KYC profile. If the profile was deleted, create a new one before retrying. | info | No | 404 |
| DALP-0463 | A template with this name already exists in this organization. | The organization already has a non-system template with the submitted name. | Choose a unique template name or update the existing template instead. | info | No | 409 |
| DALP-0467 | Caller wallet does not match the configured treasury wallet for the maturity-redemption feature. | ERC-20 approve must be called from the wallet that owns the funds. The authenticated caller is not the configured treasury wallet, so this route cannot proxy the approval. | Retry signed in as the configured treasury wallet. | info | No | 403 |
| DALP-0471 | No active claim found for topic {topicId} on identity {identityAddress}. | Platform API could not find an active (non-revoked) claim matching the requested topic on the target identity. | Verify the topic and identity address, and confirm the claim has not already been revoked, before retrying. | info | No | 404 |
| DALP-0489 | Webhook timestamp is outside the accepted replay window. | The compliance webhook timestamp was more than five minutes away from the server clock. | Send a fresh provider event with a current timestamp and verify clock synchronization for the provider. | info | No | 400 |
| DALP-0501 | Compliance provider cannot transition to the requested state. | The provider is not in a state that permits the requested operation (for example, resume requires paused; revoke is terminal). | Refresh the provider and choose an operation that matches its current state. | info | No | 409 |
| DALP-0502 | Compliance provider not found. | No compliance provider matching the requested ID exists within the calling organization. Cross-organization lookups are concealed and return the same response as an unknown provider ID. | Confirm the provider ID was created by and belongs to your organization, then retry the request. | info | No | 404 |
| DALP-0507 | Webhook replay rate limit exceeded. | The tenant has exhausted the replay-specific webhook rate-limit bucket. | Wait for the Retry-After interval before starting another replay. | info | Yes | 429 |
| DALP-0508 | Webhook replay range is out of order or too large. | The replay range ends before it begins, or spans more blocks than one request may replay without confirming the large range. | Send a range whose end is at or after its start. For a large range, split it into smaller ranges or confirm the large range, then retry. | info | No | 400 |
| DALP-0512 | Webhook endpoint URL is not allowed. | The endpoint URL resolves to a private, loopback, link-local, or otherwise disallowed network range. | Use a publicly reachable HTTPS endpoint that does not resolve to a private network address. | info | No | 400 |
| DALP-0516 | Webhook endpoint has pending delivery attempts. | Changing the endpoint URL re-targets queued deliveries; disabling the endpoint cancels them. | Wait for the queue to drain, or re-send the request with ?acknowledgePending=true to confirm the effect on queued deliveries. | info | No | 409 |
| DALP-0517 | Fat-event acknowledgment is missing required field paths. | A fat endpoint delivers unredacted personal data for its active subscriptions. Every <eventType>.<fieldPath> that the thin shape would strip must be named in fatEventsAcknowledgment.fieldsAcknowledged for the resulting subscription set. The acknowledgment on this request (or the stored one, when the request omits it) does not cover that set, so the platform rejected the update rather than silently widening consent. | Resend the PATCH with fatEventsAcknowledgment.fieldsAcknowledged set to the full list returned by getWebhookFatAcknowledgmentFields for the subscriptions that will be active after the update. The Console's switch-to-fat dialog computes this list automatically. | info | No | 422 |
| DALP-0526 | Webhook endpoint not found. | No webhook endpoint with that identifier exists in the current tenant, or the endpoint has been deleted. Deleted endpoints remain as audit tombstones and are not available for new operations. | Verify the endpoint identifier belongs to the authenticated tenant. If the endpoint was deleted, create a new endpoint. | info | No | 404 |
| DALP-0527 | Webhook delivery not found. | No delivery record matches the combination of delivery identifier, endpoint identifier, and tenant. On the receipt-create path, this also surfaces when the delivery's own counterSignedReceipts snapshot is false, meaning the feature was not enabled on the endpoint when that delivery was dispatched. | Confirm the delivery identifier and endpoint identifier are correct and belong to the authenticated tenant. List deliveries for the endpoint to retrieve valid identifiers. | info | No | 404 |
| DALP-0529 | Webhook receipt not found. | No receipt record with that identifier exists in the current tenant scope. | Verify the receipt identifier belongs to the authenticated tenant. Use the receipt list endpoint to retrieve valid identifiers. | info | No | 404 |
| DALP-0533 | Metadata not found. | Platform API could not resolve the metadata payload from IPFS or the configured object-storage mirror. | Verify the metadata hash and retry after the metadata source has replicated. | info | No | 404 |
| DALP-0534 | Webhook subscription pattern is not recognized. | The subscription pattern does not match any registered webhook event type or documented wildcard form, or it requests retracted events without a matching source subscription that can create the rows retractions are derived from. | Use an exact registered event name, a lifecycle wildcard (_.pending, _.provisional, _.final, _.retracted, .recalled), a prefix wildcard for a registered event family (token.transfer.), or *. Pair every retraction pattern with a pending, provisional, or final source subscription. | info | No | 400 |
| DALP-0535 | Webhook endpoint URL must use HTTPS. | The endpoint URL uses a scheme other than HTTPS. Untrusted destinations must be HTTPS so delivery traffic is encrypted and the SSRF guard can apply its public-address policy. | Register an https:// URL, or ask an operator to add this exact origin to DALP_WEBHOOKS_TRUSTED_DESTINATIONS on a private-network install that needs plain HTTP. | info | No | 400 |
| DALP-0537 | Webhook Idempotency-Key reused. | The Idempotency-Key already started a registration from a different request, a registration that never completed, or one whose endpoint has since been deleted. | Send a new Idempotency-Key for a new registration, and reuse a key only to retry the identical request. | info | No | 409 |
| DALP-0605 | The requested token features contain an incompatible pair. | The requested token features contain an incompatible pair. | Remove one feature from every reported incompatible pair and retry. | info | No | 409 |
| DALP-0606 | No yield available to claim. A prior conversion consumed the yield for completed periods. | The claim-yield preflight found that quoteAccruedWad returned zero and the holder's consumedInterestWadExact is positive while accrual is still open. The yield that would have been claimable was offset by interest consumed during a prior token conversion. | Wait for the next yield period to complete after the conversion. Check the conversion history to see which periods were consumed. | info | No | 400 |
| DALP-0608 | No yield available to claim for this holder. | The holder has no claimable yield. Periods may already be claimed, accrual may be closed after conversion, or consumed interest may have offset the accrued amount. | Verify holder eligibility (last claimed period, conversion state) before retrying. | info | No | 400 |
| DALP-0615 | Hashlock reveal not required for this XvP settlement. | Revealing a secret applies only to HTLC-enabled XvP settlements with external flows; the target settlement is local-only. | Skip the reveal call for local settlements, or target an HTLC settlement that has external flows. | info | No | 400 |
| DALP-0616 | smart-wallet executor not available. | The X-Executor header requested smart-wallet execution while platform Account Abstraction is disabled. | Use X-Executor: eoa or omit the header until platform Account Abstraction is enabled. | info | No | 403 |
| DALP-0621 | smart-wallet executor not available. | The X-Executor header requested smart-wallet execution while Account Abstraction is disabled for this organization. | Ask your organization administrator to enable Account Abstraction for this organization, or omit the X-Executor header to use the organization's default routing. | info | No | 403 |
| DALP-0639 | observedAt exceeds the chain time drift allowance. | The feed observation is more than 300 seconds ahead of the selected chain time. | Synchronize the submitting clock with the selected chain and retry. | info | No | 400 |
| DALP-0645 | The requested metadata key is not declared in any accessible asset-type template. | Token list grouping and metadata filters resolve eligible keys from asset_type_templates.metadataSchema visible to the caller's tenant scope. The requested key is not declared in any of those schemas, so it cannot be used as groupBy or as a filter[metadata.<key>] axis. | Verify the key name matches a field declared in a system or organization template's metadata schema. Use data.availableKeys (capped, alphabetically sorted) for a quick discovery list, or meta.facets["metadata.<key>"] on a regular list request for the authoritative bucketable axes. | info | No | 400 |
| DALP-0646 | Continuous-type metadata key not eligible for grouping or facets. | Token list groupBy and facet axes are restricted to bucketable metadata field types (string, enum, country-code, currency-code, address). Continuous types such as number, date, decimal-money, percentage, bps, and url are filterable via filter[metadata.<key>] but not bucketable. | Pick a bucketable-typed key for groupBy and faceting, or apply this key as a filter only. | info | No | 400 |
| DALP-0647 | Identifier-type metadata keys not eligible for grouping or facets. | Identifier-typed metadata fields (isin, cusip, lei, figi) are typically unique per token. Using them as groupBy yields degenerate one-token-per-group results and as facet axes they yield single-bucket noise, so token list excludes them from both surfaces. | Use the identifier key as a filter via filter[metadata.<key>], or pick a non-identifier bucketable-typed key for grouping and facets. | info | No | 400 |
| DALP-0653 | Treasury address missing for the maturity-redemption or fixed-treasury-yield feature. | An attached treasury feature has no configured treasury address. | Configure a non-zero treasury address, then retry. | info | No | 404 |
| DALP-0655 | Attached treasury-bearing features disagree on treasury, denominationAsset, or treasuryIsContract. | Attached treasury features disagree on treasury configuration. | Align the treasury, denomination asset, and implementation classification, then retry. | info | No | 409 |
| DALP-0657 | Requested block not yet reached by the historical balance indexer. | The requested atBlock value is ahead of the indexer head for the historical-balances feature; no checkpoint slice covers it yet. | Wait for the indexer to catch up to the requested block, or pick a lower block from the picker's latest-indexed default. | info | Yes | 409 |
| DALP-0670 | A user with this email already exists. | Each platform user must have a unique email address. | Use a different email or open the existing user in User management. | info | No | 409 |
| DALP-0679 | The sale token cannot be withdrawn as a payment currency. | The selected withdrawal currency is the token being sold; the contract reserves those tokens for buyers and reverts CannotWithdrawSaleToken. | Choose one of the sale's payment currencies instead of the sale token, then retry. | info | No | 400 |
| DALP-0681 | A precondition on the request was not met. | The If-Match or If-None-Match condition sent with the request does not hold for the current resource: it was changed, created, or removed since the version the request was built against. | Read the resource again, apply your change to the version you just read, and send the request with the entity-tag from that read. | info | No | 412 |
| DALP-0684 | The requested airdrop was not found. | No airdrop at the requested address has been indexed for the active chain, so there is nothing to return. | Confirm the airdrop address and that it has been deployed and indexed, then retry. | info | No | 404 |
| DALP-0686 | The purchase is off the sale's subscription step. | The sale accepts only cumulative subscriptions that are a multiple of its purchase increment, and this payment buys a token amount that leaves the buyer's total off that step; the contract would revert PurchaseNotMultipleOfIncrement. | Pick a token amount on the sale's subscription step and send the exact payment for it, then retry. | info | No | 400 |
| DALP-0694 | Excluding the holders of this claim needs an acknowledgement from a named actor. | A NOT branch of the compliance rule excludes the holders of a claim they carry on their own identity, so a holder can delete that claim and pass the rule. The control does not hold on its own, and accepting that is a decision that must carry a name, which is why an impersonated session cannot make it. | Send holderRemovableNot.accepted as true from a session that is not impersonated. Or use an identity block-list, whose identities you enumerate in IdentityBlockListComplianceModule and the holder holds no key to edit; a country block-list, which reads the registry country field only the identity manager writes; or a positive claim for the group you admit, so a holder who deletes it loses access instead of gaining it. | info | No | 400 |
| DALP-0705 | The debug bundle time window was not accepted. | The debug bundle window has no start, no end, or an end that falls before its start. | Send a start and an end, with the end after the start, then export the bundle again. | info | No | 400 |
| DALP-0707 | Token reference is incomplete. | The asset reference cannot identify a token in its stated family. | Send an EVM contract address, or a Canton instrument id together with its instrument admin. | info | No | 400 |
| DALP-0708 | Values from two chain families were combined. | The request combines values that belong to different chain families. | Filter and address the token within one family. | info | No | 400 |
| DALP-0713 | Document upload does not match its declaration. | The uploaded document does not match what the request declared. | Upload the file again and confirm it with its real size and type. | info | No | 422 |
| DALP-0719 | The organization has too few approvers to publish. | The organization has fewer approvers than maker-checker publishing requires. | Give a second owner or administrator to the organization, then publish again. | info | No | 422 |
| DALP-0720 | The obligation configuration does not hold together. | The obligation configuration is internally inconsistent. data.violations lists every problem the platform found, so they can be corrected in one pass. | Correct every violation listed in data.violations, then save or publish again. | info | No | 422 |
| DALP-0733 | Portfolio resource was not found. | The requested portfolio resource does not exist in the active organization. | Verify the identifier and the active organization, then request it again. | info | No | 404 |
| DALP-0734 | The ballot wasn't accepted. | The ballot did not satisfy one of the rules a cast has to pass. The reason field names which one. | Read reason, correct that one condition, and send the ballot again. | info | No | 422 |
| DALP-0736 | The external token wasn't registered. | The address did not pass on-chain ERC-20 metadata verification, or it is already registered. | Check that the address exposes name, symbol, and decimals on this chain, and that it is not registered already. | info | No | 422 |
| DALP-0746 | The anchor question cannot be answered as asked. | An anchor lookup takes exactly one of a document digest, a subject identity or a registry address, and a verification takes the artifact's parts in order within the published ceilings. data.reason names which of those the request broke. | Read data.reason. Send one of digest, subject or registry to read registry entries, or send each part's SHA-256 and byte length in delivery order, with issuer, to check a document you hold. | info | No | 422 |
| DALP-12019 | The selected custody account cannot sign for this request. | Signing this request needs a custody account that is active, eligible on the network the request resolved to, and bound to a live provider signer. The account in data.custodyAccountId misses at least one of those: it is still provisioning, its account or organization context left the active state, its provider reports an unhealthy signer, or its managed key binding is gone. When data.custodyAccountId is absent, the request named no account and the signed-in participant holds no eligible primary account on this network. When data.reason is present, this organization cannot drive the account's wallet and the value names the capability it lacks, the same reason the custody-account list reports for that account. | Read the custody-account list for the network this request targets, pick an account it reports as active and eligible, and send that identifier. Ask an administrator to provision or repair an account on that network when the list offers none. | info | No | 409 |
| DALP-12020 | The token claim request does not match the token's indexed identity state. | Before it signs a claim, the platform checks the requested topic against the token's topic registry chain, the claim data against the topic scheme, and the claim it is asked to revoke against the indexed claims; one of those checks refused the request. data.reason names which. | Read data.reason, then correct the topic, the claim data, or the claim selection to match the token's topic scheme and indexed claims. | info | No | 422 |
| DALP-12021 | The token is not in a state that accepts this lifecycle change. | The platform checked the indexed token before it queued the transaction: a redemption needs a positive amount or an available balance, and a maturity needs an unmatured bond whose contract holds the denomination balance. data.reason names the check that failed. | Read the token, then send the request that matches its current state: a positive redeemable amount, a bond that is not yet mature, or a bond contract funded with its denomination asset. | info | No | 422 |
| DALP-12022 | The transfer-approval request does not match the token's indexed identity state. | The platform resolves the wallet in the token identity registry and checks that the acting executor identity is an approval authority; one of those lookups found no indexed match. data.reason names which one. | Register the wallet in the token identity registry, or select an executor whose identity is an approval authority, wait for indexing, then retry. | info | No | 422 |
| DALP-12023 | The forced-transfer request has no complete transfer item. | A forced transfer moves tokens from an owner to a recipient; the request left out the owner, the recipient, or the amount of at least one item. | Send at least one item with an owner, a recipient, and an amount, then resubmit. | info | No | 422 |
| DALP-12024 | This token does not support a batch transferFrom. | The token contract exposes a single-item transferFrom only. The platform refuses the batch before it signs anything, so no partial batch reaches the chain. | Submit each transferFrom as its own request. | info | No | 422 |
| DALP-12026 | Prices cannot be set on this token. | Setting a price needs the token's access-control interface to confirm the administrator; the indexed token reports neither ERC-3643 nor the supported SMART interface. data.tokenAddress names the token. | Use a supported token contract, or correct the indexed token interface metadata, then retry. | info | No | 422 |
| DALP-12028 | The compliance parameters do not match the selected module schema. | The platform decodes each module's parameters against that module's own schema before it encodes them for the chain; data.issues lists every field that failed. | Correct each field listed in data.issues, then submit the request again. | info | No | 422 |
| DALP-12030 | The token feature configuration is not accepted. | The token create workflow validates every feature configuration against the feature catalog before it deploys; at least one feature configuration failed that validation. | Correct the feature configuration named in the message, then submit the token creation again. | info | No | 422 |
| DALP-12031 | The request is well formed but cannot be applied to the current state. | The route understood the request and refused it against the current domain state. The refusing check publishes no error entry of its own, so this general 422 stands in for it. | Read message, correct the request or the state it depends on, then retry. Include the request id if you contact support. | info | No | 422 |
| DALP-12033 | This operation needs wallet verification. | The operation signs with the caller's wallet, and the request carried no walletVerification block, so the platform stored nothing. | Add walletVerification with the method this account has enrolled, a PIN, an authenticator code, a recovery code, or an identity-provider code, then send the request again. | info | No | 400 |
| DALP-12075 | This deployment does not create new assets of that legacy family. | The asset family in data.type stays supported for deployments that already issue it, but the platform creates no new assets of that family. The deployment has not opted in with features.legacyAssetCreation, so the creation is refused before any contract is deployed. | Create the asset from a DALP asset template instead. Set FEATURE_LEGACY_ASSET_CREATION=true on this deployment when it still issues legacy assets. | info | No | 422 |
| DALP-12076 | The token operation cannot be built from the fields supplied. | A field the operation needs is missing, or the combination requested has no on-chain form: a bond without a maturity date, a role change whose target shape does not parse, a compliance module change without the address that identifies the module, or a batch transfer variant the token does not implement. | Correct the field named in the message and submit the operation again. | info | No | 422 |
| DALP-12095 | Off-chain metadata values for token {tokenAddress} do not match its template. | The token's asset-type template declares a type, allowed options, or bounds for each off-chain metadata key, and at least one submitted value falls outside them. Every rejected key is listed with its reason. | Correct the listed keys against the template's field definitions, then submit the metadata again. | info | No | 400 |
| DALP-12096 | Off-chain metadata key {key} on token {tokenAddress} is immutable and already set. | The token's asset-type template marks this off-chain key immutable, and a value for it is already stored, so it can neither change nor be removed. | Leave the stored value in place, or resubmit it unchanged alongside the other keys. | info | No | 400 |
| DALP-12099 | Mark refreshed less than ten minutes ago. | The mark of this subject was refreshed inside the ten-minute cooldown, so the platform fetched nothing and the stored mark is unchanged. | Wait for the window the Retry-After header reports, then refresh the mark again. | info | Yes | 429 |
| DALP-12110 | Profile section not found. | No profile section with this id is visible to the active organization; sections owned by another organization answer the same way. | List GET /api/v2/settings/profile-sections and retry with an id from that page. | info | No | 404 |
| DALP-12112 | A profile field a profile version filled cannot be removed or change its storage, audience, type, choices, or mutability. | Every profile version records which fields held a value. Removing such a field, moving it between on-chain and off-chain storage, changing who fills it, changing its type, dropping one of its choices, or loosening an immutable field would orphan, expose, or invalidate a value an earlier version holds; data.keys lists the locked fields. | Keep those fields as they are, or add a new field with the other settings. | info | No | 409 |
| DALP-12114 | The storage or mutability of a metadata field cannot change while deployed tokens use the template. | Tokens deployed from the template already carry metadata under its keys; moving a field between on-chain and off-chain storage would leave one key in both stores, removing an immutable field would orphan a value that cannot change, and loosening an immutable field would let a later write replace a value that was immutable when it was written. data.keys lists the locked fields. | Keep the storage and mutability of those fields as they are, or add a new field under a key no deployed token holds. | info | No | 409 |
| DALP-12133 | The profile image upload was rejected. | An uploaded object is missing, differs from the declared byte size, is not a PNG, or is not exactly 256 px or 64 px square. The platform deleted both uploaded objects. | Render both renditions as square PNG at 256 px and 64 px, upload them again, and confirm with the actual byte sizes. | info | No | 400 |
| DALP-12140 | An organization section may not take the slug of a system section. | Filled profile fields are recorded as <section slug>.<field key>, so an organization section whose name derives a system section's slug would shadow it; data.slug names the slug. | Choose a section name that derives a different slug. | info | No | 400 |
| DALP-12151 | A profile section a profile version filled cannot be deleted. | A participant holds a value for a field of the section, or a profile version of the organization recorded one, and deleting the section would orphan that value. | Retire the section instead of deleting it; earlier versions keep its values. | info | No | 409 |
| DALP-12159 | The members and links do not form one complete issuance. | The members, structure, templates, or feature links in the request do not form one complete issuance. data.reason names the rule the request broke. | Read data.reason. Send every structure member once with its declared template, or declare every link a standalone member needs, then retry. | info | No | 422 |
| DALP-12161 | The issuance run was not found. | The run does not exist in the active organization and system. | Use the run identifier returned when the issuance was accepted in this organization and system. | info | No | 404 |
| DALP-12162 | Wallet removal refused. | The wallet still holds a token balance, is the last address registered to its identity, still signs for a smart wallet, or cannot sign in one of its organizations. Nothing was submitted. | Resolve what the message names, then request the removal again. | info | No | 409 |
| DALP-12193 | Too many requests for this operation. | The caller exceeded a rate or attempt limit on this operation. The refusing limit publishes no error entry of its own, so this general 429 stands in for it. | Wait before retrying. Honour a Retry-After header when the response carries one. | info | Yes | 429 |
| DALP-12195 | Choose a primary custody account for this participant and network. | The acting participant has no usable primary custody account for this organization and network. No other account is substituted, even if one is eligible. | Choose a primary custody account in this network, or explicitly select one for this request. | info | No | 409 |
| DALP-12196 | The selected custody account is not eligible for this request. | The selected account is not available to the acting participant in this organization and network, or is not active and eligible for the request. No other account was substituted. | Select an active eligible account from this participant's custody-account list for this organization and network. | info | No | 409 |
| DALP-12235 | The Canton instrument was not found. | No Canton instrument with this admin and id is disclosed to the parties of the calling organization on the selected network. | Use an instrument admin and id from the Canton assets list, and select the network the instrument lives on with X-Network-Id. | info | No | 404 |
| DALP-12236 | The contract a forced removal skips still exists. | A forced removal drops the registry entry without archiving the contract the normal removal archives, so it is the recovery path for a contract that is already gone. This one still exists. | Take the normal route of this operation, which archives the contract named here. Force the removal only once that contract is gone. | info | No | 409 |
| DALP-12245 | The price has more decimal places than the feed stores. | The feed stores prices at a fixed number of decimals, and the submitted price cannot be written at that precision without rounding. | Round the price to the feed's decimals, then submit it again. | info | No | 400 |
| DALP-12246 | The feed update batch cannot be submitted. | The batch holds more feeds than the ceiling allows, names one feed twice, or every update in it would revert on chain. | Split the batch, give each feed at most one update, and check the nonce, deadline, and issuer authorization of each update. | info | No | 409 |
| DALP-12247 | No feed on this network prices the currency. | The exchange-rate graph for the selected network has no feed that quotes the requested currency. | Use a currency from the supported-currencies list, or add an exchange-rate feed for the currency on this network. | info | No | 422 |
| DALP-12251 | Platform request could not be read. | The request contains a field the platform cannot accept for this operation. | Check the request fields against the operation's accepted values, then retry. | info | No | 400 |
| DALP-12257 | Custody account not found. | No custody account visible to the caller in the active organization matches this identifier. | Refresh the active organization's account list and choose an account returned there. | info | No | 404 |
| DALP-12260 | The user or session was not found. | The security operation names a user or a session that does not exist, or that the caller may not see. | Check the user or session identifier and confirm the caller may administer that user, then retry. | info | No | 404 |
| DALP-12261 | Multi-signer wallets are switched off on this deployment. | This deployment serves single-signer wallets only, so a signer set with more than one signer or a threshold above one is refused. | Keep the draft at one signer and a threshold of one, or ask an operator to enable multi-signer wallets. | info | No | 403 |
| DALP-12263 | The market calendar cannot produce trading sessions. | The calendar names a timezone the platform cannot resolve, session times or an exception that never open a session, or a private continuous market schedules a pre-open. | Use an IANA timezone and session times with pre-open at or before open and open before close. Leave pre-open empty for every weekday and open exception on a private continuous market, then submit the calendar again. | info | No | 422 |
| DALP-12264 | The market setting cannot be changed. | A listed market keeps its matching mode and private flag. | Keep the matching mode and private flag of a listed market unchanged, or list a new market with the settings you need. | info | No | 422 |
| DALP-12267 | The requested account type is not the one this organization drives. | An organization drives one account type on a network: a smart account where account abstraction is enabled and reconciled, an EOA everywhere else. The walletType sent names the other one. | Omit walletType and let the organization's own account type stand, or send the type it drives. | info | No | 400 |
| DALP-12271 | The custody provider configuration is not valid here. | The provider or ledger the configuration names is not enabled on this deployment, or the configuration is not created under the organization the caller is authenticated for. | Choose a provider and ledger this deployment enables, and create the configuration under the caller's own organization. | info | No | 422 |
| DALP-12274 | The custody proof does not bind this account. | The control proof, external control artifact, provider binding, or step-up confirmation sent with this request does not bind the account on this ledger, or the custody provider does not support the ledger. | Produce a new proof or confirmation for this account and ledger, then send the request again. | info | No | 422 |
| DALP-12286 | The compliance module settings contradict each other. | Two or more settings in the submitted compliance module configuration cannot hold at the same time. | Submit one consistent module configuration. | info | No | 422 |
| DALP-12287 | The compliance expression is too broad to enforce. | The compliance expression has no positive condition that narrows who it admits. | Add a positive condition, or acknowledge the allowed warning. | info | No | 422 |
| DALP-12295 | No network is configured for this chain id. | No network in the platform configuration matches the chain id the request named. | Send a chain id the platform has configured, or ask an administrator to add the network. | info | No | 404 |
| DALP-12296 | No network is configured under this name. | No network in the platform configuration matches the network name the request named. | Send a network name the platform has configured, or ask an administrator to add the network. | info | No | 404 |
| DALP-12301 | No executor network is configured for this chain. | No configured network resolves to the chain the smart-wallet executor was asked to use. | Select a configured chain, or ask an administrator to add the network. | info | No | 404 |
| DALP-12305 | The request names two networks. | The request carries both X-Chain-Id and X-Network-Id, so it names two networks. | Send only one scope header: X-Chain-Id for an EVM network or X-Network-Id for a Canton network. | info | No | 400 |
| DALP-12306 | The X-Network-Id header is blank. | The X-Network-Id header is present but blank, so it names no platform network. | Send the stable name of the network you want, or omit the header. | info | No | 400 |
| DALP-12308 | The X-Custody-Account-Id header is not a custody account identifier. | The X-Custody-Account-Id header value is not a valid custody account identifier. | Send an identifier the custody-account list returns, or omit the header. | info | No | 400 |
| DALP-12311 | The external wallet signature does not authorize this request. | The external-wallet signature sent with this request does not authorize the prepared signing payload. | Reconnect the selected account and sign the payload returned for this exact request. | info | No | 400 |
| DALP-12321 | Workflow not found. | No workflow visible to the caller's organization matches this identifier. | Use the workflow identifier returned to the organization that started it. | info | No | 404 |
| DALP-12325 | The settlement secret was not accepted. | The settlement secret or its signature failed validation or cryptographic processing. | Send the original secret and a valid signature for this settlement. | info | No | 422 |
| DALP-12328 | The token-sale document was rejected. | The token-sale document's type, size, visibility, or hash does not meet the upload rules. | Correct the document type, size, visibility, or hash, then upload it again. | info | No | 422 |
| DALP-12342 | The role is not one this token grants. | The role in the request is not a role this token's access manager grants. | Send one of the roles the token's access control lists. | info | No | 400 |
| DALP-12345 | No token deployment is recorded under this transaction. | No token deployment visible to the caller is recorded under the transaction in the request. | Use the transaction identifier the token create request returned. | info | No | 404 |
| DALP-12369 | The network definition cannot be stored. | The network definition cannot be stored as submitted. | Correct the named field of the network definition, then save it again. | info | No | 400 |
| DALP-12386 | The wallet signature was not accepted. | The signature in externalMessageAuthorization does not recover to the wallet of the custody account in data.custodyAccountId over the deployment payload this request prepared, or its deadline is no longer current. | Send the request again without a signature to read the current payload, sign that exact payload with the account's connected wallet, then send the fresh signature. | info | No | 400 |
| DALP-12390 | The wallet signature was not accepted. | The signature in externalMessageAuthorization does not recover to the wallet of the custody account in data.custodyAccountId, or it covers something other than the payload this request prepared. | Send the request again without a signature to read the current payload, sign that exact payload with the account's connected wallet, then send the fresh signature. | info | No | 400 |
| DALP-12392 | The sale's terms documents are fixed. | A terms document can change only while the sale is in setup and its terms hash is not yet set. This sale has left setup, or its terms hash is set or being set, so the terms investors accept can no longer change. | Keep the current terms documents. Other document types still upload and delete as usual. To offer different terms, create a new sale. | info | No | 409 |
| DALP-14019 | The instrument template is unpublished for your organization. | Your organization does not currently offer this instrument template for issuance. A DALP Library template stays unpublished until your organization publishes it, and a published template can be unpublished again. | Publish the template from the Instrument templates overview, or call PUT /api/v2/settings/asset-type-templates/:id/publish, then create the token again. | info | No | 409 |
| DALP-14020 | An instrument template of this issuance is unpublished for your organization. | Your organization does not currently offer the instrument template of one member for issuance. A DALP Library template stays unpublished until your organization publishes it, and a published template can be unpublished again. | Publish the template from the Instrument templates overview, or call PUT /api/v2/settings/asset-type-templates/:id/publish, then review and accept the issuance again. | info | No | 409 |
| DALP-14024 | The instrument structure of this issuance is unpublished for your organization. | Your organization does not currently offer this instrument structure for issuance. A DALP Library structure stays unpublished until your organization publishes it, a published structure can be unpublished again, and a structure reads unpublished while one of its member templates is unpublished. | Publish the structure from the Structures tab of Instrument templates, or call PUT /api/v2/settings/asset-type-template-structures/:id/publish, then review and accept the issuance again. | info | No | 409 |
| DALP-14025 | {payerAddress} is not a wallet this organization pays gas from on this network. | Withdrawals move funds out of the organization's relayer, bundler or operator wallet on the request's network. The address is none of them. | Withdraw from a relayer, bundler or operator wallet listed on the Funding tab of Transaction funding for this network. | info | No | 404 |
| DALP-14026 | Withdrawing a paymaster's EntryPoint deposit is not available yet. | The paymaster holds its funds as an EntryPoint deposit, which is released by an unlock followed by a withdrawal. That two-step withdrawal is not available yet. | Leave the deposit in place; it keeps sponsoring transactions. | info | No | 422 |
| DALP-14027 | At most {withdrawableWei} wei can be withdrawn from this wallet now. | The wallet keeps enough to pay for the withdrawal itself, including a replacement at a raised fee, so a withdrawal cannot take its whole balance. | Withdraw no more than the withdrawable amount, which the withdrawable read of the same wallet returns. | info | No | 422 |
| DALP-14028 | {destination} cannot receive this withdrawal. | The destination is the zero address, the wallet the funds would leave, or an address that reverts a plain native transfer. data.reason names which. | Name a different destination address. | info | No | 422 |
| DALP-14029 | This transaction is owned by a workflow and has no executable call to retry. | The transaction request is a workflow status handle. Its owning workflow drives the executable transaction requests, so retrying this handle cannot replay the write. | Inspect the owning workflow and force-retry only its failed executable transaction request. | info | No | 409 |
| DALP-14031 | Transaction preparation not found. | The platform has no transaction preparation with that id for the calling user in this organization. A preparation another user created, or one that belongs to another organization, is reported the same way as a missing one to prevent enumeration. | Use the preparationId that the prepare call returned to you. If you no longer have it, prepare the operation again and authorize the new preparation. | info | No | 404 |
| DALP-14032 | This custody account cannot authorize a transaction preparation. | A preparation needs an active custody account that you hold in this organization, on the requested network, with a provider that lets you sign yourself. The account this request relies on does not meet those conditions. An account that does not exist, or that another user or organization holds, gets this same answer. | Prepare the operation with an externally signing custody account that you hold in this organization on the requested network. An account whose keys a managed custody provider holds does not use preparations: send its operations through their regular API routes, and the platform signs them. | info | No | 422 |
| DALP-14033 | The request does not match how the transaction preparation is bound. | A preparation fixes its signing method, executor, custody account and operation when you create it, and every later call must match them. This request sends a claim, user operation or authorization artifact for a different signing method or executor, or an artifact kind this route never accepts. A create request gets this answer when its idempotency key already names a different preparation, or when the smart wallet already has an open operation its owner signs. | Read the preparation and send the claim, attachment or artifact that matches its signingMethod and executor. Use a new idempotency key for a different operation. Finish or let expire the open owner-signed operation before you prepare another on the same smart wallet. | info | No | 409 |
| DALP-9077 | Token {tokenAddress} matured; minting closed for maturity-redemption tokens. | Maturity-redemption tokens stop ordinary issuance once they are matured. The redemption budget is fixed to the token supply at maturity. | Do not mint this token after maturity. Use the existing maturity treasury top-up path to fund redemptions, or issue a new instrument if new supply is required. | info | No | 409 |
| DALP-9084 | The X-Chain-Id header must be a numeric chain id. | The X-Chain-Id header value did not pass the chain-id format check: the value must be a positive decimal integer with no leading zeros, no greater than 2147483647 (the largest supported chain id). | Send a numeric chain id within the supported range (for example 31337), or omit the header to target the organization's default network. | info | No | 400 |
| DALP-9085 | The requested network is not available for this organization. | The X-Chain-Id header names a network the active organization has no active system on, or the organization has not enabled multi-network support. The organization deploy route also uses this code when the network picked for a first system is not one the platform offers and has bootstrapped. | Switch to the organization's default network, or add the network in organization settings after enabling multi-network support. During onboarding, pick one of the networks the deployable-networks read returns. | info | No | 400 |
| DALP-9086 | The requested network is not ready for this organization. | The organization has the requested network registered, but its system is not active: the deployment is still pending or running, has failed, or the network was disabled. | Check the network's status in organization settings; wait for the deployment to finish or retry it, then retry the request. | info | No | 409 |
| DALP-9090 | No organization is available to invite this person into. | The membership service could not resolve an organization to invite into: the current session may have no organization selected, or the acting account may no longer hold a membership in the organization it points at. | Select an organization the acting account belongs to and send the invitation again. If one is already selected, ask an organization owner to confirm the acting account is still a member of it. | info | No | 404 |
| DALP-9094 | This request's API key has sent too many requests. | The credential presented with this request has used up the requests its rate limit allows inside the current time window, so the invitation was never attempted. | Wait for the current rate-limit window to pass, then send the invitation again. Space bulk invitations out over a longer period, or ask an organization owner to raise the request allowance on this key. | info | Yes | 429 |
| DALP-9140 | Governance poll not found. | Platform API could not find the poll in the authenticated tenant scope. | Verify the poll identifier and tenant context before retrying. | info | No | 404 |
| DALP-9141 | Governance poll is not accepting ballots. | Ballots are only accepted between the poll's open and close times while the poll status is open. | Check the poll's opensAt and closesAt window; ballots submitted after close are rejected even if signed before close. | info | No | 409 |
| DALP-9143 | Ballot was signed over a different poll definition. | The definition hash in the signed ballot does not match the poll's current immutable definition, so the signature does not cover this poll. | Fetch the poll again and re-sign the ballot over its current definitionHash. | info | No | 409 |
| DALP-9144 | Ballot signature verification failed. | The signature does not verify against the claimed voter address. Undeployed smart wallets and ERC-6492 wrapped signatures are not accepted. | Sign the exact PollBallot typed data with the claimed voter wallet and retry. Smart wallets must be deployed on-chain. | info | No | 422 |
| DALP-9146 | Voter has zero voting power at the poll record date. | Ballot weight resolves from the indexed voting-power snapshot at the poll's record date; a zero-weight ballot is rejected. | Only wallets with delegated voting power at the record date can cast ballots on this poll. | info | No | 422 |
| DALP-9147 | Caller lacks the governance role on the token. | Creating or closing a poll requires the governance role on the token whose holders are polled. | Ask a token admin to grant the governance role to one of your wallets, then retry. | info | No | 403 |
| DALP-9151 | Governance instance not found. | No governor and timelock pair is deployed for this token by a factory in the authenticated system. | Create the first proposal through the Console to bootstrap the token's governance pair, or verify the governor address. | info | No | 404 |
| DALP-9152 | Governance proposal not found. | The proposal id is not indexed on the given governor within the authenticated system. | Verify the governor address and proposal id; freshly created proposals appear once indexed. | info | No | 404 |
| DALP-9153 | Proposal configuration is out of bounds. | Record date, voting period, execution delay, or quorum violates the protocol bounds or the governance instance's quorum floor. | Adjust the schedule parameters to the documented bounds (record date now+24h to now+90d, period 1-30 days, delay 24h-30d, quorum at or above the instance floor) and retry. | info | No | 422 |
| DALP-9154 | Executable action is not in the curated catalog. | Proposals may only carry curated governance-role single-call operations; the composed action's target or selector is outside the catalog or the feature is not attached to the token. | Compose the proposal from catalog actions on features attached to the token. | info | No | 422 |
| DALP-9155 | Timelock lacks the governance role on the token. | Executable proposals run through the timelock, which must hold the governance role on the token's access manager before the vote is created. | Grant the governance role to the timelock on the token's access manager, then retry. | info | No | 409 |
| DALP-9158 | Vote already cast on this proposal. | On-chain governance votes are final; one ballot per wallet per proposal. | No action is available. The recorded ballot stands. | info | No | 409 |
| DALP-9160 | Voting-power feature cannot be detached during open votes. | The token's governor has proposals that are not yet executed, defeated, or canceled; detaching the voting-power feature would invalidate their electorate. | Wait for open proposals to reach a terminal state (or cancel them), then retry the detach. | info | No | 409 |
| DALP-9164 | Poll ballot rate limit exceeded. | Too many ballot submissions arrived from this caller for this poll in a short window. | Wait for the Retry-After interval before submitting another ballot. | info | Yes | 429 |
| DALP-9169 | Multi-network support cannot be disabled while additional networks are in use. | At least one non-default network has a system that is deploying or active; disabling the opt-in would orphan it. | Wait for in-flight network deployments to finish, then remove the additional networks before disabling multi-network support (network removal is not yet available). | info | No | 409 |
| DALP-9182 | This feature cannot be detached while attached features depend on it. | Other features attached to this token declare this feature as a dependency in the feature registry. Detaching it would break their on-chain accounting; for example a dividend or interest feature reads the balance checkpoints that historical-balances records at each record date. | Detach the dependent features first, then retry detaching this feature. | info | No | 409 |
| DALP-9243 | The token creation values cannot be processed. | The token creation input cannot be represented by the durable workflow schema. | Correct the reported token amount or price fields and retry the request. | info | No | 422 |
| DALP-9252 | The metadata key cannot be used for this asset query. | The requested metadata key is unknown or is not eligible for the selected filter or grouping operation. | Use one of the available metadata keys that supports this query operation. | info | No | 422 |
| DALP-9269 | The sort field is not supported on this list. | List endpoints accept only the sortable fields declared for that collection. An unknown or non-sortable field name cannot order the page. | Use one of the sortable fields documented for this list endpoint, or omit sort to keep the default order. | info | No | 400 |
| DALP-9270 | List endpoints accept a single sort field. | The collection query codec supports one sort field per request. Comma-separated multi-field sort is not implemented on the shared list infrastructure. | Send a single field in sort (prefix with - for descending) and retry. | info | No | 400 |
| DALP-9271 | The filter field is not supported on this list. | List endpoints accept only the filterable fields declared for that collection. An unknown or non-filterable field name cannot narrow the page. | Use one of the filterable fields documented for this list endpoint, or remove the unknown filter key. | info | No | 400 |
| DALP-9272 | The filter operator is not supported. | Each collection filter accepts only the operators defined for that field. An unknown operator cannot be applied safely to the list query. | Use a documented operator for the field (for example eq, iLike, inArray, or between) and retry. | info | No | 400 |
| DALP-9273 | The membership filter list is too large. | Membership filters (inArray and notInArray) cap the number of values so SQL IN clauses stay bounded and predictable. | Send at most 100 values in the membership list, or split the request across multiple pages or batches. | info | No | 400 |
| DALP-9274 | The page limit is out of range. | Every collection list bounds page size to an integer between 1 and 200 so a single request cannot pull an unbounded result set. | Set page[limit] to an integer from 1 through 200 and use pagination links for additional rows. | info | No | 400 |
| DALP-9275 | The page offset is out of range. | Collection list offsets must be integers of zero or greater. A negative offset is not a valid start position for a page. | Set page[offset] to an integer greater than or equal to 0. | info | No | 400 |
| DALP-9281 | Organization not found. | No organization matches the requested id. | Confirm the organization id from the platform-admin organization list, then retry. | info | No | 404 |
| DALP-9289 | Token list filter uses an unsupported operator or value. | The governedByCaller and governedByExecutor filters accept only eq with the string true or false. Other operators or values do not describe the affordance gate. | Send filter[governedByCaller][eq]=true or filter[governedByCaller][eq]=false (same for governedByExecutor). | info | No | 400 |
| DALP-9298 | The market was not found. | The market id does not name a listed market in your organization, so the platform has nothing to read or operate on. | Use a market id from the markets list of your organization. | info | No | 404 |
| DALP-9299 | The order was not found. | The order id does not name an order placed by a wallet the selected participant controls, so the platform has nothing to read or cancel. | Use an order id from the working-orders list of the selected participant. | info | No | 404 |
| DALP-9302 | The order was refused before it reached the book. | An intake check failed: identity-registry eligibility, desk limits, the trading authorization, the signed fee cap, expiry, the order signature, or the submission rate. | Correct the order against the rejection reason in the response, then submit a new signed order. | info | No | 422 |
| DALP-9303 | The wallet's reserved balance cannot cover this order. | The order must reserve more than the wallet has left. Two limits apply: the trading authorization the wallet gave this venue, minus what the wallet already reserves on this venue; and the wallet's holdings, minus what it already reserves on all venues. | Cancel resting orders to release reserved balance, raise the wallet's trading authorization for this venue, or submit a smaller order. | info | No | 409 |
| DALP-9305 | The market cannot make this transition. | The requested market operation is not valid for the market's current status: for example resuming a market that is not halted, or halting one that is not live. | Check the market status on the venue-operations surface, then issue a valid transition. | info | No | 409 |
| DALP-9306 | The market-data stream could not be opened. | The stream request named a market this deployment does not serve, or the request came from another origin. | Open the stream same-origin against a live market id from the markets list. | info | No | 404 |
| DALP-9311 | The Canton party wallet was not found. | No Canton party wallet matches this party id in the active organization, so the platform returned no record. | Use a wallet id from the wallets list of the active organization. | info | No | 404 |
| DALP-9323 | Asset reference names neither a token contract nor a Canton instrument. | The shared asset read addresses an EVM token by its contract address and a Canton instrument by its instrument id plus the instrumentAdmin party that completes the key. The path segment is not an address and no instrumentAdmin was sent, so the request names nothing the platform can look up. | Send a token contract address, or send the instrument id together with instrumentAdmin. | info | No | 400 |
| DALP-9324 | Filter names a column the asset's chain family does not have. | A shared collection under one asset, its holders or its events, advertises both families' columns, and the asset decides which family answers. The filter names a column from the other family, and the answering family has no such column to evaluate it against. The refusal names the field, the family, and the columns that family does publish on the collection that was read. | Filter on a column the named asset's family has, or read the asset in the family whose columns you are filtering on. | info | No | 400 |
| DALP-9330 | The token operation request does not describe a valid operation. | The request does not describe an operation the ledger can carry out: a transfer window that has already passed in ledger time, a transfer addressed to the party sending it, a contract that belongs to a different instrument than the route names or that the caller's scope does not carry, an addon whose operating party is not the instrument admin, a treasury account the admin does not own alone, or a feature config its module cannot be built from. The platform prepared no command. | Send an executeBefore later than the current ledger time, address a transfer to a party other than the sender, name the contracts of the instrument the route addresses, and operate an addon as its instrument admin with a treasury the admin owns. | info | No | 400 |
| DALP-9355 | The filter value is not an option this field supports. | Enum-backed filters answer only the options their field declares. A value outside that set names a selection no row can hold, and dropping the filter instead would answer a wider page than the caller asked for. | Send one of the options documented for that field and retry, or use inArray for a membership list. | info | No | 400 |
| DALP-9414 | The trade bust was refused before any reversal. | A pre-check failed: the trade is not chain-confirmed, an order on it is still open, the bust window has passed, the trade is already busted or proposed, a counterparty or fee account lacks balance, or the compliance path is blocked or unavailable. The reason in the response names the failed check. | Resolve the named reason, then propose the bust again. | info | No | 422 |
| DALP-9415 | The maker-checker rules refused this decision. | The proposer can never approve or reject their own proposal, a proposal that already carries a decision accepts no second one, and a decision route accepts only records of its own kind. The violation in the response names the rule. | Ask a different venue operator to decide the proposal, or refresh the approvals list to see its current state. | info | No | 409 |
| DALP-9430 | X-Executor has no matching execution mode. | The X-Executor header does not name a supported execution mode. | Use eoa or smart-wallet, or omit X-Executor to use the organization default. | info | No | 400 |
| DALP-9432 | This executor does not exist on the selected network. | The eoa and smart-wallet executors are EVM account shapes. The selected chain family uses another signing model. | Omit X-Executor on this network and use its custody-held signing account. | info | No | 400 |
| DALP-9433 | The selected executor is unavailable. | The selected participant has no usable account for the requested executor. When data.reason is present, this organization cannot drive the participant's wallet and the value names the capability it lacks, such as account abstraction not being enabled on this chain. The platform never substitutes the wallet's signer key. | Select an available executor or provision the participant smart wallet, then retry. | info | No | 409 |
| DALP-9518 | Topic name {topicName} does not match topic id {topicId}. | The request supplied both a topic name and a topic id, and the id computed from the name differs from the id given. | Use the computed topic id or submit only one topic identifier. | info | No | 409 |
| DALP-9519 | Contract {feedAddress} does not expose the feed interface. | The contract at the given address did not answer the required feed interface on the selected chain. | Verify the feed address and confirm the contract is deployed on the selected chain. | info | No | 422 |
| DALP-9531 | Sort names a column the asset's chain family cannot order on. | The events collection under one asset advertises both families' sort keys, and the asset decides which family answers. An EVM token's events order on block time and a Canton instrument's order on its ledger offset, so a sort naming the other family's column leaves the answering projection with no column to order the page by. A page ordered on something else would be published either under the column that was asked for, describing it wrongly, or under another, which is not the page that was asked for. The refusal names the field, the family, and the columns that family can be ordered on. | Sort the events on a column the named asset's family can be ordered on, omit sort to take that family's own ordering, or read the asset in the family whose column you are sorting on. | info | No | 400 |
| DALP-9534 | The issuer identifier and the request body name different chain families. | A trusted issuer is named by an address on one family and by a party id on the other, and this request mixed them: the issuerId segment and the body must describe the same family. The platform submitted no command and changed nothing. | Send the identifier that matches the body, or send the body that matches the identifier, then retry. | info | No | 400 |
| DALP-9540 | Approval request was not found. | No approval request exists under this identifier in the calling organization. | Read the approvals list for the current identifier and state, then decide again. | info | No | 404 |
| DALP-9542 | Operations case was not found. | No operations case exists under this identifier in the calling organization. | Read the cases list for the current identifier, then acknowledge the case that carries it. | info | No | 404 |
| DALP-9563 | V1 compliance modules cannot be installed on a v2 asset: {modules}. {remedies}. | A DALP asset is a v2 token. A v1 compliance module looks for the older token interface, which a v2 token does not report, so it would reject every mint. data.typeIds lists the v1 modules in the request, and data.remedies names the v2 module that replaces each one. | Replace each module in data.typeIds with its -v2 module, for example collateral-v2 instead of collateral. A module without a v2 version cannot be used on a DALP asset yet; remove it from initialModulePairs. | info | No | 400 |
| DALP-9564 | V1 compliance modules cannot be installed on a v2 asset: {modules}. {remedies}. | A DALP asset is a v2 token. A v1 compliance module looks for the older token interface, which a v2 token does not report, so once installed it would reject every mint. data.typeIds lists the v1 module in the request, and data.remedies names the v2 module that replaces it. | Install the -v2 module instead, for example collateral-v2 instead of collateral. A module without a v2 version cannot be installed on a DALP asset yet. | info | No | 400 |
Authentication errors
| DALP Code | Message | Why | Suggested Fix | Severity | Retryable | HTTP Status |
|---|---|---|---|---|---|---|
| DALP-0002 | Authentication missing or failed. | The request did not include valid authentication credentials. | Authenticate again or send a valid API key/session credential. | info | No | 401 |
| DALP-0004 | User not onboarded. | The authenticated user has not completed onboarding required for this operation. | Complete onboarding and retry the request. | info | No | 403 |
| DALP-0005 | Two-factor authentication required. | The operation requires wallet-signing protection that is not configured for this user. | Set up PIN or two-factor authentication and retry. | info | No | 401 |
| DALP-0036 | This authentication method or API key scope is not permitted for this request. | The presented authentication method or API-key scope is not permitted for this request. | Use a permitted session or an API key with the required scope. | info | No | 403 |
| DALP-0345 | An on-chain identity is required to set a token price. | The authenticated participant has no on-chain identity on the request chain. | Create or select a participant identity on the request chain, then retry the token price update. | info | No | 403 |
| DALP-0472 | Step-up authentication required for this operation. | The route requires a recent re-authentication and the current session is older than the policy window. | Re-authenticate (sign in again or complete the step-up challenge) and retry the request. | info | No | 403 |
| DALP-0488 | Webhook authentication failed. | The compliance webhook signature or URL token could not be verified against the provider credentials. | Verify the provider webhook URL and signing secret configuration, then send a freshly signed event. | info | No | 401 |
| DALP-0510 | Webhook signature verification failed. | The webhook signature, timestamp, or signed payload did not verify against the expected signing material. | Verify the signing secret, timestamp tolerance, and exact raw request body before retrying. | info | No | 401 |
| DALP-0659 | Identity provider verification failed. | The authenticator code did not pass the identity provider's verification for this signing request. | Enter a fresh code from your authenticator app and try the operation again. | info | No | 403 |
| DALP-12034 | The requested wallet verification method is not enrolled. | The request named a wallet verification method this account has never enrolled, so no credential exists to check it against. | Enroll the method in wallet security settings, or send a method this account already holds. | info | No | 401 |
| DALP-12253 | Session required. | The request lacks the authentication or wallet context required for this operation. | Check that the active session or API key has access to the required wallet, then retry. | info | No | 401 |
| DALP-12292 | The compliance provider rejected its credentials. | The compliance provider refused the credentials configured for it. | Rotate or correct the provider credentials, then send the request again. | info | No | 400 |
| DALP-9093 | This request's API key was rejected. | The credential presented with this request is unknown, switched off, past its expiry, over its usage allowance, or tied to a blocked account, so the invitation was never attempted. | Rotate to an active API key, re-enable the existing one, or raise its usage allowance, then send the invitation again. | info | No | 401 |
| DALP-9188 | Session authentication evidence is incomplete. | The request session did not include the linked authentication providers needed to authorize the call. | Sign in again, then retry the request. | info | No | 401 |
| DALP-9438 | Login two-factor authentication setup is required. | This deployment requires interactive users to enroll login two-factor authentication before calling authenticated APIs. | Open the two-factor setup page, enroll an authenticator app, then retry the request. | info | No | 403 |
Permission errors
| DALP Code | Message | Why | Suggested Fix | Severity | Retryable | HTTP Status |
|---|---|---|---|---|---|---|
| DALP-0003 | This operation is not available to the caller. | The route runs behind an access gate that the caller does not satisfy. When data.requiredRoles is present, it lists the roles that pass the gate and the wallet that authorized this request holds none of them. When it is absent, the gate is an off-chain permission or an ownership scope the caller sits outside. | Retry with an actor that already holds one of the roles in data.requiredRoles, or ask an administrator to grant one of them. When the record is the caller's own, confirm the request names that record on the network where the caller's account lives. | info | No | 403 |
| DALP-0006 | This action requires a role the acting wallet does not hold. | The token or system contract restricts this action to the {{requiredRoles}} role, and the acting wallet was granted no matching role. | Ask an administrator to grant the {{requiredRoles}} role, then retry, or perform this action with a wallet that already holds it. | info | No | 403 |
| DALP-0032 | Insufficient role for this operation. | The operation requires elevated permissions and the authenticated actor does not hold the role required for this route. | Retry with an account that has the role required by this route, or check the route documentation for the required role. | info | No | 403 |
| DALP-0034 | Active organization required for this operation. | The request requires organization-scoped permissions, but the session does not have an active organization selected. | Select an organization, refresh the session, and retry the request. | info | No | 403 |
| DALP-0147 | The active organization does not have the required permission for this operation. | The permission check on the active organization failed. The organization has not been granted the off-chain permission required by this route. | Ask an administrator to grant the required permission to this organization, then retry. | info | No | 403 |
| DALP-0148 | The authenticated user does not have the required permission for this operation. | The permission check on the authenticated user failed. The user has not been granted the off-chain permission required by this route. | Ask an administrator to grant the required user-level permission, then retry. | info | No | 403 |
| DALP-0320 | Access denied to restricted document. | The requested document has restricted visibility. The platform checked the caller's token roles and found neither a governance nor an admin role on this token. | Use credentials for an account that holds a governance or admin role on this token, or request that an administrator share a non-restricted copy of the document. | info | No | 403 |
| DALP-0353 | Delegated redemption requires the custodian role. | Redeeming for owner {owner} requires the custodian role. | Use the caller wallet as owner or grant the caller the token custodian role. | info | No | 403 |
| DALP-0357 | Provided system addon does not belong to the authenticated system. | The systemAddon filter address supplied in the request is not one of the token sale addon addresses registered under the authenticated system. | Use a systemAddon address from the list of addons returned by the system addons endpoint for the authenticated system. | info | No | 403 |
| DALP-0511 | Webhook event not found. | The event does not exist or is not available to the current actor for recall. | Verify the event identifier and use an actor with webhook recall permissions. | info | No | 404 |
| DALP-0524 | The selected participant is not available. | The selected participant does not exist or cannot be assumed by the authenticated user. | Select an authorized participant or request an administrator grant. | info | No | 403 |
| DALP-0671 | Live actions feed requires Console origin. | The live actions feed carries browser session cookies, and the request origin did not match the Console origin accepted for live updates. | Refresh the Console and retry the actions view. API clients should call GET /v2/actions instead of the stream. | info | No | 403 |
| DALP-0712 | This operation is not available to the caller. | The acting wallet holds none of the roles this operation requires. | Ask an administrator to grant one of the listed roles on this token. | info | No | 403 |
| DALP-0715 | A compliance rule refused the transfer. | A compliance rule on this token refused the transfer. | Clear the named compliance blocker, then transfer again. | info | No | 403 |
| DALP-0724 | The filing period is outside the reach-back window. | The filing period is older than the reach-back window its obligation allows. | Raise the obligation's reach-back window before filing against a period this old. | info | No | 409 |
| DALP-0751 | Only a token manager can dismiss an external token. | Dismissing an external token hides it from the organization's holdings, portfolio, holder lists, token catalog, token details, and marks, and stops the platform from registering it again. It requires the tokenManager role on the organization's system. | Ask a system administrator to grant you the tokenManager role, then retry. | info | No | 403 |
| DALP-12018 | The caller's custody account lives on a different network. | This read is scoped to network {{chainId}}, the network the request resolved to, and the signed-in participant holds no custody account there. Custody accounts are registered one network at a time, so an account created on another network owns nothing here and no role grant changes that. | Switch the active network to the one that holds the caller's custody account, or send X-Chain-Id with that network's chain id. Ask an administrator to provision a custody account on network {{chainId}} when the caller needs access there. | info | No | 403 |
| DALP-12035 | The wallet verification credential was not accepted. | The supplied credential does not match the enrolled one, or it was already used. data.remainingAttempts reports how many attempts remain before verification locks. | Enter the current code or PIN and send the request again. A recovery code works once, so use a fresh one. | info | No | 403 |
| DALP-12036 | Wallet verification is locked after repeated failures. | Wallet verification failed too many times in a row for this account, so the platform locked it and stored nothing. | Wait the number of seconds in data.retryAfterSeconds, then verify again. | info | No | 429 |
| DALP-12113 | System profile sections are read-only. | System sections are shared by every organization, so no organization can change them; an organization may only retire one for itself. | Create an organization section with the fields you need instead. | info | No | 403 |
| DALP-12132 | The profile image key belongs to another user. | The object key is not under the signed-in user's own user-images prefix, or it contains a path segment the platform refuses. | Send back the hero object key the upload-url call returned for this session. | info | No | 403 |
| DALP-12136 | This API key filled its request window. | This key used its full request allowance for the current window, so the platform did not authenticate the request. | Wait for the key's request window to reopen, then send the request again. | info | No | 429 |
| DALP-12232 | You may not decide this Canton command. | Only an eligible approver other than the submitter, such as an organization owner or platform administrator, can decide a Canton command intent. | Ask an eligible approver to record the approval decision. | info | No | 403 |
| DALP-12242 | The acting wallet cannot manage feeds on this system. | Feed writes need the feeds manager role on the system, and the executing wallet does not hold it. | Ask a system administrator to grant the feeds manager role to the executing wallet, then retry. | info | No | 403 |
| DALP-12243 | The feed update was not signed. | The custody policy for the issuer key refused to sign this feed update. | Review the custody policy for the issuer key, or submit the update with an identity that the policy allows to sign. | info | No | 403 |
| DALP-12252 | Platform access denied. | The caller cannot perform this platform operation. | Ask a platform administrator for access before retrying. | info | No | 403 |
| DALP-12255 | KYC record not found. | No KYC record visible to the current caller matches this request. | Confirm the record belongs to the active organization and use an identifier returned for that organization. | info | No | 404 |
| DALP-12259 | This session may not revoke sessions. | Revoking a user's sessions needs the identity-manager role on the active organization's system, and none of the caller's wallets holds that role. | Use a session whose active organization grants one of your wallets the identity-manager role, then retry. | info | No | 403 |
| DALP-12262 | The trade-bust reversal was refused. | A reversal runs only from an approved bust record the caller may execute, and only with the approval, settled batch, and legs that record carries. This request broke one of those rules, or its reversal could not be queued or recorded as busted. | Re-read the approval and execute exactly the legs it carries. If they already match, read the approval state before you retry. | info | No | 403 |
| DALP-12266 | A role on this venue is required. | Replacing a market calendar needs the venue-admin role and market operations need the venue-operator role on this venue's access manager; data.role names the one this request needs. None of the caller's wallets holds it, and a role on another venue grants nothing here. | Ask the venue's admin to grant the role to your wallet on this venue's access manager, then repeat the request. | info | No | 403 |
| DALP-12276 | The custody approval for this request was refused. | The approval this operation waited on was rejected, the selected account cannot approve the request, or the requested custody scope is not available to the caller. | Start a new request with an account that can approve it, or ask the approver to approve the operation. | info | No | 403 |
| DALP-12278 | The caller is not a signer of this wallet. | The wallet's signer set does not include the caller's account, or that account is not eligible to sign for it. | Send the request from an account the wallet lists as an eligible signer. | info | No | 403 |
| DALP-12283 | Compliance module not found for this scope. | The requested compliance module does not apply to the system or token scope in the request. | Address the module through a system or token scope it applies to. | info | No | 404 |
| DALP-12353 | Setting the token price needs the token's administrator role. | The caller does not hold the role that may set this token's price. | Send the request as a participant with the token's administrator role, or ask one to set the price. | info | No | 403 |
| DALP-12384 | The step-up challenge does not match this request. | A wallet-verified request redeems a single-use step-up challenge issued to the caller for the active organization, this route, its target, and this exact payload. The request carried none, or one that is unknown, expired, or issued for another request, so the platform stored nothing. | Request a fresh challenge from POST /api/v2/step-up-challenges for this exact request, then send it once with the challenge id in the X-Step-Up-Challenge header. | info | No | 403 |
| DALP-14014 | The platform admin or organization owner role is required. | Creating a trading venue or listing a market is restricted to a platform admin or an owner of the organization, and this account holds neither role. | Ask a platform admin or an owner of the organization to make this request. | info | No | 403 |
| DALP-9089 | This organization has reached its limit on pending invitations. | The number of invitations still awaiting a response in this organization sits at the configured ceiling, so no further invitation can be created. Any invitation that was still pending for this address was cancelled first and was not replaced. | Cancel or accept some of the outstanding invitations, then send this invitation again to restore the cancelled one. | info | No | 403 |
| DALP-9096 | This account cannot invite members to this organization. | The organization did not accept this invitation request from the acting account, so no invitation exists for the address. | Ask an organization owner to confirm that the acting account may invite members and that the organization is ready to take new members, then send the invitation again. Check the invitations list as well, because an invitation that was pending for this address may have been cancelled by this attempt and would need re-issuing. | info | No | 403 |
| DALP-9167 | Multi-network changes require an organization administrator. | Enabling multi-network support and adding networks are organization-admin operations; the calling session is neither a platform admin nor an organization owner. | Use an account that holds the organization owner role (or platform admin), then retry. | info | No | 403 |
| DALP-9196 | This custody operation requires organization-owner access. | Changing custody credentials affects every wallet in the organization. | Retry as an organization owner or platform administrator. | info | No | 403 |
| DALP-9315 | The custody provider blocked this Canton signature. | The organization's custody provider refused to sign the Canton digest, so the platform stopped the submission. | Resolve the custody provider policy denial, then submit a new Canton command. | info | No | 403 |
| DALP-9322 | This custody account is not enabled for Canton signing. | The signing account behind this organization is not enabled for Canton Ed25519 signing, so the platform created nothing. | Use an organization whose custody account is enabled for Canton signing, then submit the request again. | info | No | 403 |
| DALP-9439 | The selected executor lacks a required blockchain role. | The selected request executor does not hold any of the indexed blockchain roles required by this route. | Use an executor with one of the required roles, or grant that role before retrying. | info | No | 403 |
| DALP-9485 | The selected executor lacks the required token role. | The token access manager does not grant this executor the role required by the operation. | Use an executor with a role listed in requiredRoles, or ask a token administrator to grant it. If no role is listed, inspect the token access manager for this operation. | info | No | 403 |
| DALP-9487 | This document requires a token holding. | The selected wallet has no positive holding in the token whose document was requested. | Select a wallet holding this token before reading the document. | info | No | 404 |
| DALP-9488 | This document is restricted. | The requested document is restricted to an audience that excludes the current caller. | Ask the issuer for document access or sign in as an authorized document reader. | info | No | 404 |
| DALP-9523 | A global platform administrator is required. | The authenticated user is not a global platform administrator. | Authenticate as a global platform administrator and retry the request. | info | No | 403 |
| DALP-9561 | Webhook request has no deployed system. | The request resolved no deployed system for the endpoint to subscribe to. | Reissue the request under a system the active tenant has deployed. | info | No | 404 |
Domain rule errors
| DALP Code | Message | Why | Suggested Fix | Severity | Retryable | HTTP Status |
|---|---|---|---|---|---|---|
| DALP-0025 | The token contract at the provided address lacks the required interface. | The target token does not expose the interface required for this operation. | Use a compatible token contract or enable the required interface before retrying. | info | No | 422 |
| DALP-0026 | System not created. | The DALP system bootstrap has not completed for this environment or organization. | Create or finish deploying the system before calling this operation. | warning | No | 403 |
| DALP-0131 | The feed round was not found. | Feed {feedAddress} has no readable round {roundId}. | Request an existing round from a feed whose history mode retains it. | info | No | 404 |
| DALP-0315 | Token creation workflow failed during phase execution. | The token deployment workflow failed in one of its phases. | Inspect the phase failure, correct the deployment inputs, and submit a new operation. | info | No | 422 |
| DALP-0318 | The user address has no associated identity contract. | The selected participant has no on-chain identity on the request chain. | Create or select a participant identity on the request chain, then retry. | info | No | 403 |
| DALP-0343 | Token price cannot be resolved from the indexed pricing state. | data.reason names the failed price state: token-not-visible has no indexed token; no-feed has no registered feed; feed-not-indexed has no indexed row; registration-date-missing has no indexed registration date; inactive-feed is disabled; unsupported-quote does not quote a supported fiat currency; unanswered-feed has no observation; and stale-feed is outside the configured window. | Read data.reason, then register, reindex, activate, correct, answer, or refresh the feed as that state requires. | error | No | 503 |
| DALP-0346 | Price feed system is not installed; ask an administrator to install it before setting a price. | The active system has no issuer-signed price-feed factory. | Install the price feed system before setting token prices. | error | No | 503 |
| DALP-0375 | Token {tokenAddress} is paused; unpause it before transferring. | The token is paused, so transfers are disabled. | Unpause the token before transferring. | info | No | 409 |
| DALP-0388 | Cannot approve version with status "{value}". Approval requires a version under review. | The KYC profile version is not in the under_review state. The approval route reads the version with a row lock and checks its status before transitioning it to approved. | Submit a KYC version for review first (POST /v2/kyc-profile-versions/:versionId/submissions), then retry the approval once the version reaches under_review status. | info | No | 409 |
| DALP-0389 | Cannot fulfill request with status "{value}". Fulfillment requires an open request. | The KYC action request is not in the open state. The fulfill route checks the request status before marking it fulfilled, and the request has already been fulfilled or cancelled. | Verify the current status of the action request before retrying. Only open action requests can be fulfilled. | info | No | 409 |
| DALP-0390 | Cannot reject version with status "{value}". Rejection requires a version under review. | The KYC profile version is not in the under_review state. The rejection route reads the version with a row lock and checks its status before transitioning it to rejected. | Confirm the version is currently under_review before calling the rejection endpoint. A version that is already approved, rejected, or still a draft cannot be rejected. | info | No | 409 |
| DALP-0391 | Cannot submit version with status "{value}". Submission requires a draft version. | The KYC profile version is not in the draft state. The submit route reads the version with a row lock and checks its status before transitioning it to under_review. | Confirm the version status is draft before submitting. A version that is already under_review, approved, or rejected cannot be submitted again. | info | No | 409 |
| DALP-0392 | Cannot update version with status "{value}". Updates require a draft version. | The KYC profile version is not in the draft state. The update route reads the version with a row lock and rejects writes to any version that has already been submitted for review, approved, or rejected. | Create a new draft version to make further changes, or check whether the existing draft can be cloned from the approved version. | info | No | 409 |
| DALP-0462 | Compliance template modules and controls must match the selected module set. | The template contains configured modules or required controls from a different compliance module generation. | Remove the incompatible controls or create a template with the matching legacy/current module set. | info | No | 422 |
| DALP-0474 | PriceResolver addon missing on system {systemAddress}. | No PriceResolver addon is installed on the target system. | Install the PriceResolver addon on the system before resolving prices. | info | No | 404 |
| DALP-0491 | Compliance provider is not accepting webhook events. | The webhook target is not currently available for compliance event intake. | Verify the provider configuration and resume the provider before sending more provider events. | info | No | 404 |
| DALP-0492 | Compliance provider is in a failed state. | The compliance provider failed provisioning or health checks and cannot process provider events. | Repair or reprovision the provider before retrying webhook processing. | info | No | 409 |
| DALP-0493 | Compliance provider event has no supported mapping. | The provider payload did not match a supported ClaimSource verdict or monitoring-alert shape and was persisted for audit. | Review the provider event type and update the adapter mapping before replaying the event. | info | No | 422 |
| DALP-0500 | Compliance webhook signing secret rotation grace period expired. | The pending webhook signing secret expired before it was promoted to the active secret. | Start a new secret rotation and update the provider dashboard with the active webhook signing secret. | info | No | 410 |
| DALP-0509 | Webhook endpoint disabled. | The endpoint is disabled and cannot accept live, replay, or test deliveries until it is re-enabled. | Re-enable the endpoint after fixing the delivery failure cause, then retry. | info | No | 409 |
| DALP-0513 | Webhook endpoint limit reached. | The tenant has reached the maximum number of webhook endpoints allowed for this environment. | Delete an unused endpoint or contact support to raise the tenant endpoint limit. | info | No | 409 |
| DALP-0523 | Transaction fee rates frozen. | Transaction fee rates for the token are permanently frozen on the feature. | Leave the frozen rates unchanged or configure a different token feature. | info | No | 409 |
| DALP-0538 | Webhook registration still in progress. | Another request with the same Idempotency-Key is still registering its endpoint. | Retry the identical request with the same Idempotency-Key after a few seconds. | info | Yes | 409 |
| DALP-0617 | Platform AA disabled; per-org AA requires platform AA enabled. | The organization setting requested Account Abstraction routing while the platform-wide Account Abstraction feature is disabled. | Keep AA_ENABLED disabled, or enable platform Account Abstraction before enabling the organization setting. | info | No | 403 |
| DALP-0637 | Account abstraction identity sync found a different smart-wallet OnchainID. | A participant's smart wallet is already registered to a different OnchainID than the participant's EOA. | Review the participant identity binding before enabling account abstraction. | info | No | 409 |
| DALP-0638 | Account abstraction identity sync found a different smart-wallet controller. | An existing smart-wallet row points at a controller that does not match the participant's current signing EOA. | Repair the participant wallet pairing before enabling account abstraction. | info | No | 409 |
| DALP-0674 | The supplied custody credentials failed validation. | The credential probe against the custody provider failed: the payload was malformed, authentication was rejected, the probe timed out, or the credentials cannot reach the organization's pinned workspace. | Verify the credential values with your custody provider, confirm they belong to the organization's workspace, and try again. | info | No | 422 |
| DALP-0675 | Custody credentials were rotated too recently. | Credential rotation enforces a minimum interval between rotations so in-flight signing operations can drain on the previous credential version. | Wait for the indicated retry interval to elapse, then submit the rotation again. | info | Yes | 429 |
| DALP-0677 | This organization's custody configuration has been destroyed and cannot be modified. | An operator destroyed the organization's custody credentials; the record is retained as a tombstone and lifecycle writes against it are rejected to prevent silent resurrection with deleted credentials. | Re-onboard the organization's custody through the explicit re-onboarding path, or contact support with the request id. | info | No | 409 |
| DALP-0678 | The custody provider for this organization is locked and cannot be changed. | The organization's custody provider was locked when its first wallet was created; switching providers would orphan existing keys. | Keep the locked provider and supply replacement credentials for it instead of selecting a different provider. | info | No | 409 |
| DALP-0683 | No airdrop addon is deployed in this system. | Listing or reading airdrops needs at least one airdrop factory registered in the active system, and this system has none. | Deploy an airdrop addon for this system, then retry the request. | info | No | 404 |
| DALP-0685 | The requested airdrop belongs to another system. | The airdrop at this address was deployed under a different system than the active one, so this endpoint does not return it. | Read this airdrop from the system that owns it, or pick an airdrop deployed in the active system. | info | No | 404 |
| DALP-0687 | Template is not ready to publish. | The publish readiness check found at least one required control with no configured module of that type on the template; data.gaps names the specific controls. | Open the Controls & Rules step for each control listed in data.gaps, configure a compatible module for it (or remove it from required controls), save the template, and retry publish. | info | No | 422 |
| DALP-0693 | This claim topic may not be used in exclusions in this system. | A NOT branch of the compliance rule excludes the holders of a claim the system's claim policy manager has set to Not allowed. Excluding those holders is defeated by its own subject: the holder manages their own identity and can delete the claim to pass the rule. | Use an identity block-list, whose identities you enumerate in IdentityBlockListComplianceModule and the holder holds no key to edit; a country block-list, which reads the registry country field only the identity manager writes; or a positive claim for the group you admit, so a holder who deletes it loses access instead of gaining it. The claim policy manager can also change the topic's setting for this system. | info | No | 422 |
| DALP-0699 | A reindex is already running on this network. | This network already has a reindex transition in flight, and the platform runs one at a time. | Wait for the running reindex to finish, then start the next one. | info | No | 409 |
| DALP-0706 | Token not found. | The token is not present in the serving projection. | Confirm the token reference and wait for indexing if it was created recently. | info | No | 404 |
| DALP-0709 | The token is paused. | The token is paused, and this operation changes balances. | Unpause the token, then run the operation again. | info | No | 409 |
| DALP-0711 | The token's state does not allow this write. | The token's current state does not allow this write. | Read the token, resolve the named condition, and write again. | info | No | 409 |
| DALP-0718 | This obligation cannot be edited. | The obligation is frozen: a published version keeps existing filings explainable, and a platform catalog obligation is the same in every deployment. | Read data.reason. Publish a new version instead of editing the published one, and copy a catalog obligation before changing it. | info | No | 409 |
| DALP-0721 | The submission's state does not allow this act. | The filing lifecycle does not permit this act from the submission's current state. | Read the submission again and choose an act its current state permits. | info | No | 409 |
| DALP-0722 | The submission changed before this act was applied. | The submission changed between the read and the write, so this act lost the race. | Read the submission again and repeat the act against the row version it now carries. | info | Yes | 409 |
| DALP-0723 | Sign-off was refused. | A separation-of-duties or bind-to-bytes rule refused the sign-off. data.reason names which one. | Read data.reason, then have a different signed-in approver review the current artifact and approve the version they read. | info | No | 409 |
| DALP-0725 | Another report generation holds this slot. | Another generation holds this organization's slot, or the lease or read model moved under this run. | Start the generation again once the running one finishes. | info | Yes | 409 |
| DALP-0726 | The period starts before the platform's recorded history. | The reference period begins before the earliest date the platform has recorded history for. | File this period outside the platform; it predates the named date. | info | No | 422 |
| DALP-0727 | Anchoring could not be turned on. | A configuration check refused anchoring for this obligation. data.reason names which check. | Read data.reason: register the issuer for the document-hash topic, give its managed signer a claim key, choose a warning severity where publication is the fulfilment act, and confirm the disclosure with a written reason. | info | No | 409 |
| DALP-0728 | The reporting record was not found. | No reporting record of the requested kind with that identifier is visible to the caller in the active organization. A record another organization or another investor holds answers the same way, so the reply never confirms that an identifier exists elsewhere. | List the records of that kind, such as obligations, statements, or confirmations, and use an identifier from that list. | info | No | 404 |
| DALP-0730 | This token is already registered. | The token address is already registered as an external token for this organization. | Open the existing registration instead of registering the address a second time. | info | No | 422 |
| DALP-0738 | This filing has no stored artifact. | No artifact was ever stored for this submission, so there is nothing to download and nothing was erased. A split artifact is served as its parts, an erased one answers with its tombstone, and one under legal hold stays retrievable; none of those reaches this error. | Read the submission's state. An artifact exists only once generation has written one, so wait for the filing to be generated or read a submission that already has been. | info | No | 409 |
| DALP-0744 | The filing period or submission was not found. | No filing period or submission with that identifier is visible to the active organization. data.subject names which of the two was addressed. A row another tenant owns answers the same way, so the reply never confirms that an identifier exists elsewhere. | List the organization's filing periods and submissions, and use an identifier from that list. | info | No | 404 |
| DALP-0747 | This filing cannot be anchored yet. | An anchor may only fire from a discharged filing, and this submission has not been acknowledged or published. Before that the artifact can still legitimately be regenerated, and a commitment to a digest that may still change is one a document holder would later fail to reproduce, with no way to tell an honest regeneration from tampering. | Discharge the filing first: enter the authority's acknowledgement, or publish it to holders. Anchoring runs on its own at that act, and the retry route exists for the attempt that failed there. | info | No | 409 |
| DALP-0749 | This document cannot be anchored. | Writing a registry entry is a permanent, public disclosure that can never be corrected, only superseded by a further entry, so every prerequisite is checked before anything reaches a chain. data.reason names which one refused: the confirmation of permanence was missing, the session is an operator acting as somebody else, the subject is not a usable identity, this organization has no active system on the chosen chain, its issuer identity is inactive or has no resolvable claim key, that identity is not trusted for the document-hash topic in its own system's registry, the system carries no anchor registry, or the label would carry something identifying onto a public chain. | Read data.reason. Anchor as a signed-in owner or administrator on your own session, on a chain where your organization runs a system whose anchor-registry migration has completed, with a subject identity your issuer is trusted for, a short non-identifying label, and disclosureConfirmed set to true. A chain that was reached and declined is not this error: that arrives as data.outcome in a successful response. | info | No | 409 |
| DALP-0752 | The security of this shareholder list was not found. | No security with that contract address is indexed in the active organization's system at data.recordBlock. A security another organization issued answers the same way, so the reply never confirms that a contract address exists elsewhere. | Use the contract address of a security the organization issued, as shown in the Console. For a security created after data.recordBlock, choose a later record block, or leave the block out to use the newest final block. | info | No | 404 |
| DALP-0753 | No shareholder list can be read at this block. | The security's balance history does not reach the record block, or the record block is not final yet. data.reason names which, and data.boundaryBlock is the block the history starts at, the block the feature was detached at, or the newest final block. | For feature-not-attached, the security never had a historical-balances feature, so it has no record block to list. For feature-detached, the feature was detached at data.boundaryBlock: choose a record block before that block. For enablement-after-record-block, choose a record block at or after data.boundaryBlock. For history-incomplete, no record block can be listed, because the security had supply before the feature was attached; data.boundaryBlock is the block the feature was attached at. For record-block-not-final, wait until that block is final, or leave the block out to use the newest final block. | info | No | 422 |
| DALP-12012 | The transaction preparation has expired. | The authorization window ended before the prepared operation was finalized. | Prepare the operation again and authorize the new preparation. | info | No | 410 |
| DALP-12025 | The token exposes neither ERC-3643 nor the supported SMART access-control interface. | The platform reads the indexed token interface before it resolves roles; this token reports neither interface, so no role check can run. data.tokenAddress names the token. | Use a token that implements ERC-3643 or the supported SMART access-control interface, or correct the indexed token interface metadata, then retry. | info | No | 422 |
| DALP-12027 | This bond funds redemptions from its maturity-redemption feature treasury. | The bond has an attached maturity-redemption feature, and that feature's configured treasury pays redemptions. The legacy top-up route writes to the bond contract instead, so the deposit would never fund a redemption. | Use the maturity-redemption treasury top-up endpoint for this bond. | info | No | 422 |
| DALP-12029 | The organization signing wallet holds no claim-signer key on the issuer identity. | Signing a claim needs the organization submission wallet to hold a key with the claim-signer purpose on the issuer identity. The indexed identity data.issuerIdentityAddress holds no such key for data.walletAddress. | Add the claim-signer purpose key for the wallet on the organization identity, wait for indexing, then retry the submission. | info | Yes | 422 |
| DALP-12048 | No Corporate Action with this identifier exists on the token. | The identifier does not name a Corporate Action on this token, or it belongs to another token. | List the token's Corporate Actions and use an identifier from that list. | info | No | 409 |
| DALP-12049 | The Corporate Action is not in a status that accepts this operation. | Preview, approval, and confirm follow the drafted, previewed, approved, executing lifecycle, and this run has moved past the status the operation needs. | Read the record, then send the operation its current status accepts. | info | No | 409 |
| DALP-12050 | This Corporate Action needs a linked dividendId. | The declared dividend has not indexed onto this Corporate Action yet, so the dividend-backed operation cannot resolve its target. | Wait for the declare to index, then retry. | info | Yes | 409 |
| DALP-12051 | The cash-dividend snapshot is not ready to confirm. | Record-date finality has not been reached, so the snapshot the confirm applies is not final yet. | Preview again after record-date finality, then confirm. | info | Yes | 409 |
| DALP-12052 | Confirm requires a stored preview. | Confirm applies the allocations a preview computed, and this Corporate Action has none stored. | Request preview first, then confirm the previewed allocations. | info | No | 409 |
| DALP-12053 | The confirm does not match the stored dividend-yield snapshot preview. | The merkle root, totalEntitled, or totalRequired differs from the stored preview, or an indexed holder balance no longer converts to token base units. | Preview again and confirm with the exact values that preview returns. | info | No | 409 |
| DALP-12054 | Corporate Actions of this type complete on create. | bondCoupon, maturityRedemption, and conversion name an attached feature program and settle when created, so there is no drafted run to preview or confirm. | Operate the linked program through its own feature routes. | info | No | 409 |
| DALP-12055 | Confirm failed because the token is paused. | Pause blocks mint and burn, and this Corporate Action applies its allocations through them. | Unpause the token, then confirm again. | info | No | 409 |
| DALP-12056 | Remaining snapshot balances changed after preview and this run is aborted. | Holder balances moved between preview and confirm, so the stored allocations no longer apply. | Create a new Corporate Action and preview against the current balances. | info | No | 409 |
| DALP-12057 | Spin-off requires an empty child token. | The child token already has holders, or gained holders after the preview, so spin-off allocations cannot define its initial distribution. | Use an existing empty child token, or preview again with one. | info | No | 409 |
| DALP-12058 | Spin-off confirm requires supply-management on the child token. | Minting the spin-off allocations onto the child token needs the supply-management role, and this organization does not hold it there. | Grant supply-management on the child token to this organization, then confirm. | info | No | 409 |
| DALP-12059 | Holder balances for this record date are not available yet. | The indexer has not covered the record date, or a past record date needs the attached historical-balances feature. | Wait for indexing to catch up, or attach historical-balances, then retry. | info | Yes | 409 |
| DALP-12060 | A rights-issue tokenSale path requires an existing tokenSaleId. | The rights issue was created without a token sale, so sale-backed operations have no sale to act on. | Create the rights issue with a tokenSaleId, or use the allotment path. | info | No | 409 |
| DALP-12061 | The token-sale feature is off in this deployment. | Sale-backed rights-issue operations need the token-sale feature, and this deployment does not enable it. | Use the allotment path. | info | No | 409 |
| DALP-12062 | No indexed token sale exists at the given address. | The sale contract has not been indexed yet, or the address does not hold a token sale. | Wait for indexing to catch up, verify the address, then retry. | info | Yes | 409 |
| DALP-12063 | The token sale sells a different token, not this Corporate Action's token. | Rights-issue sale operations must target a sale whose sale token is the Corporate Action's token. | Point the Corporate Action at a sale that sells this token. | info | No | 409 |
| DALP-12065 | This idempotency key was already used for a different create. | A Corporate Action already exists for this key with different terms, so replaying would change what the first request created. | Send a new key for a new create, or repeat the identical original request. | info | No | 409 |
| DALP-12066 | The indexer carries no decimals for the token yet. | Allocation math needs the token's decimals from the indexer, and the token has not indexed. | Wait for the token to index, then retry. | info | Yes | 409 |
| DALP-12067 | Another Corporate Action is in flight for this token. | One composition Corporate Action runs at a time per token; a run that is not yet completed or aborted blocks a second one and blocks primitive mint and burn. | Wait for the in-flight run to complete or abort it, then retry. | info | No | 409 |
| DALP-12069 | The Corporate Action this run follows up on is not on this token. | followsUpOn names a run the preview reads to learn which holders are already paid, and no such run exists on this token. | Send the identifier of a Corporate Action on this token, or omit followsUpOn to start a fresh run. | info | No | 409 |
| DALP-12071 | This Corporate Action needs a feature the token does not have attached. | A dividend, coupon, redemption or conversion Corporate Action dispatches to the token's own feature contract, and this token carries no attached one for it. | Attach the feature this Corporate Action type runs on, then retry. | info | No | 409 |
| DALP-12077 | The compliance module named cannot be resolved to a single binding. | Configuring a compliance module addresses one bound module instance on the token. The token has no binding for the module type requested, or it has more than one and the single-instance request cannot say which. | Bind the module to the token first, or address the instance directly with instanceAddress when the token holds several of that type. | info | No | 422 |
| DALP-12078 | An asset with the same name, symbol, and decimals already exists. | The factory refuses a second deployment of an asset whose name, symbol, and decimals match one it already deployed, so the address it would produce is the address of the existing asset. | Use the existing asset, or change the name, symbol, or decimals before creating a new one. | info | No | 422 |
| DALP-12080 | The initial price cannot be recorded as supplied. | An initial price is stored against the denomination asset at a fixed precision. The price supplied is not well-formed, or it cannot be represented at that precision without losing value. | Supply a price with fewer decimal places, or omit the initial price and set it after creation. | info | No | 422 |
| DALP-12081 | The denomination asset cannot back a price feed. | A price feed quotes the asset in its denomination asset, and reads that asset's ERC-20 symbol() and decimals() to name and scale the quote. The denomination asset does not answer both, or its symbol is not one a feed can quote. | Denominate the asset in an ERC-20 that reports a readable symbol and decimals, or create it without an initial price. | info | No | 422 |
| DALP-12082 | The organization has no signer for price feed submissions. | A price feed update is signed by the organization's own feed signer, and the active organization has none provisioned. | Provision the organization's feed signer, then submit the price again. | info | No | 422 |
| DALP-12083 | This deployment has no price feed factory. | Creating a price feed calls the feeds factory of the active system, and no feeds factory address is configured for it. | Install the feeds factory on this system, or create the asset without an initial price and set the price later. | error | No | 422 |
| DALP-12087 | The contract rejected this token write. | The write reached the contract and the contract refused it. The on-chain state is unchanged, and the message names the condition the contract enforced. | Correct the operation against the asset's current on-chain state, then submit it again. | info | No | 422 |
| DALP-12092 | The transaction queue refused this token write. | Every on-chain token write passes the transaction queue, which refuses one it will not carry: an idempotency key already spent on a failed attempt, a request the queue settled as terminal, or a paying wallet without the funds to send it. The write never reached the contract, so the asset is unchanged. | Read the message for the condition the queue named, correct it, then submit the write with a new idempotency key. | info | No | 422 |
| DALP-12094 | The contract at {erc20Address} is not an ERC-20 token. | Recovering an ERC-20 balance needs the token's live symbol() and decimals(), and the address has no contract code or does not answer those reads. | Send the address of an ERC-20 contract held by this token, then retry. | info | No | 422 |
| DALP-12097 | The paying treasury cannot cover this redemption's cash leg. | The treasury holds less of the denomination asset than the announced burns are priced at, and nothing reserves the cash, so a run started now would stop part-paid with tokens already burned. | Fund the paying treasury with the denomination asset, then confirm again. | info | Yes | 409 |
| DALP-12098 | This confirm does not execute from the redemption's paying treasury. | The cash leg leaves the wallet that executes the confirm, so a confirm from any other wallet would measure a balance nobody spends and pay from a treasury the terms did not name. | Confirm from the wallet the terms name as the paying treasury. | info | No | 409 |
| DALP-12100 | This deployment resolves no ENS avatars. | The deployment names no ENS network, so no address carries an avatar the platform can fetch. | Ask an operator to configure the ENS network and gateway. The mark still answers the generated disc without this rung. | info | No | 422 |
| DALP-12115 | The created user's identity could not be deployed. | The chain failed the deployment of the created user's identity, so the user was not kept. | Repeat the create with a new Idempotency-Key. | error | No | 409 |
| DALP-12131 | The brand logo upload was rejected. | The brand logo upload does not meet the issued-token image rules: the token is external, or the file is not a PNG, JPEG or WebP of at most 5 MB and 2048 px a side, or its stored bytes differ from the declaration. | Upload a PNG, JPEG or WebP of at most 5 MB and 2048 px a side for a token this organization issued, then confirm it with its real size and type. | info | No | 422 |
| DALP-12142 | Declared dividends are still unclaimed. | The current {{featureName}} feature still owes declared dividends, and moving it onto a distribution waterfall would strand them on the retired feature. | Let holders claim the declared dividends until the feature reports nothing outstanding, then rotate the feature. | info | No | 409 |
| DALP-12160 | The issuance run conflicts with a newer declaration or an earlier request. | The structure or a template changed after it was reviewed, or the idempotency key already accepted a different declaration. | Reload the structure and templates, review the issuance again, and accept it with a new idempotency key. | info | No | 409 |
| DALP-12163 | This redemption pays its cash leg in the token it burns. | The cash and the burn land in one transaction, so a holder is credited the units the burn destroys and ends the run holding what they started with, while the treasury is short the amount it paid and the record reports the holder as applied. | Name a different asset as the denomination, then confirm again. | info | No | 409 |
| DALP-12164 | This redemption's cash leg needs a smart-account executor. | The cash and the burn settle in one smart-account transaction, so a holder is paid and burned together or left untouched. A plain externally owned account sends one call per transaction and has no atomic shape to offer. | Confirm from a smart-account executor, or declare the redemption without a cash leg and settle the payment separately. | info | No | 409 |
| DALP-12165 | The maker-checker rules refused this decision. | A second pair of eyes clears a Corporate Action for execution, and one of those rules said no: the caller may not decide, the session is impersonated or a machine credential, the caller raised or last previewed this record, a decision already landed on it, the record is not in a decidable state, the plan moved since it was read, the cash leg is not funded, or the approval window closed. The violation in the response names the rule. | Read the named rule. A distinct permitted operator decides from a signed-in session, on a fresh preview when the plan moved and on a funded treasury when the cash leg is short. | info | No | 409 |
| DALP-12166 | This redemption prices one or more holders at zero cash. | Cash is floored to whole base units of the denomination asset, so a holder whose units are worth less than one base unit is owed nothing. The cash and the burn land in one transaction, so confirming would destroy those holders' units and pay them nothing. | Raise the price per unit, or announce an amount that prices above zero for every holder, then confirm again. | info | No | 409 |
| DALP-12167 | This redemption's denomination asset was not issued in this system. | The cash leg is paid with a plain ERC-20 transfer inside the burn's own transaction, and the executing smart account does not read what that call returned. An asset that reports failure by returning false instead of reverting would leave the burn standing beside a payment that never moved, and only an asset this system issued is known to revert. | Name a denomination asset issued in this system, then confirm again. | info | No | 409 |
| DALP-12168 | This token charges a burn fee, so the cash leg cannot be priced. | A burn fee splits every redeemed amount into a transfer to the fee recipient and a smaller net burn. Cash priced on the announced amount therefore pays for units that stay outstanding in the fee recipient's balance, and those units can be redeemed a second time. | Set this token's burn fee to zero, then confirm again. A redemption that declares no cash leg is unaffected. | info | No | 409 |
| DALP-12171 | This Corporate Action's election window is closed. | Holder elections are accepted only while the Corporate Action's configured election deadline is open. | Submit the election before the deadline, or use a new Corporate Action. | info | No | 409 |
| DALP-12172 | The election choice is not offered by this Corporate Action. | The submitted choice is not one of the options configured for this Corporate Action. | Read the Corporate Action and submit one of its configured choices. | info | No | 409 |
| DALP-12173 | The holder is not eligible to elect on this Corporate Action. | The holder was not present in the Corporate Action's record-date eligibility set. | Submit an election only from an eligible holder account. | info | No | 409 |
| DALP-12174 | The holder wallet is not authorized to submit this election. | The authenticated wallet does not match the holder wallet authorized for the election. | Retry from the holder's authorized wallet. | info | No | 409 |
| DALP-12175 | The election deadline does not permit submission. | The configured election deadline is not in the future. | Set an election deadline after now. | info | No | 409 |
| DALP-12176 | The Corporate Action election configuration cannot be used. | The election options or their settlement terms do not form a valid Corporate Action election. | Correct the election configuration and create the Corporate Action again. | info | No | 409 |
| DALP-12177 | The Corporate Action's election deadline is still open. | Execution must wait until holders can no longer change their elections. | Wait until the configured election deadline has passed, then confirm again. | info | No | 409 |
| DALP-12178 | The Corporate Action's election window is locked. | Preview cannot be changed after the election deadline or after a holder has submitted an election. | Create a new Corporate Action or use the stored election outcome. | info | No | 409 |
| DALP-12179 | This Corporate Action has no holder-election configuration. | The election route applies only to Corporate Actions created with holder-election terms. | Read the Corporate Action and use its supported operation, or create one with an election configuration. | info | No | 409 |
| DALP-12230 | The Canton allocation request expired. | The settlement allocation request passed its execution window before the allocation was made, so the platform cannot allocate against it. | Create a new allocation request with an execution window that has not passed. | info | No | 410 |
| DALP-12231 | The Canton command already has a different approval decision. | This Canton command intent already has a terminal approval decision, and the new decision differs from it. | Read the submission and keep its recorded approval decision. | info | No | 409 |
| DALP-12234 | The Canton participant rejected the command. | The Canton participant refused the submitted command, so the ledger did not change. | Correct the cause the participant named, then submit the command again. | info | No | 422 |
| DALP-12241 | This feed operation needs an add-on the system does not have. | The operation depends on a system add-on, such as the price resolver or a feed factory, that is not installed on this system. | Install the add-on named in the error on this system, then send the request again. | info | No | 409 |
| DALP-12244 | More than one signing key matches the feed participant. | The platform found several keys that can sign for this participant and will not pick one on its own. | Keep one signing key for the participant, then submit the update again. | error | No | 503 |
| DALP-12265 | A settlement transfer leg would be refused by the token. | The platform simulates every transfer leg of a settlement batch before it submits the batch, and the token would refuse at least one of them. | Resolve the token's transfer restriction on the blocked leg, then let the batch drain again. | info | No | 409 |
| DALP-12272 | The custody provider configuration cannot take this change. | The configuration is in a state that refuses the change: something still references it, its credential source cannot change on a rotation, a newer credential version is already recorded, it holds no managed credential slot, or recovery needs a successful probe taken after the quarantine. | Read the configuration, clear what blocks the change, then send the request again. | info | No | 409 |
| DALP-12275 | This custody request is waiting for an approval. | The custody provider parked the operation until an approver acts on it, or the lifecycle request still needs its external-message authorization. | Complete the approval with the custody provider, or supply the external-message authorization, then send the request again. | info | No | 409 |
| DALP-12285 | The compliance module binding cannot make this change. | The compliance module binding the system or token holds is not in a state this write can move. | Read the binding the system or token currently holds, then address that instance. | info | No | 409 |
| DALP-12293 | The KYC document changed during this request. | Another request changed the KYC document after this request read it. | Read the current document version, then send the request again. | info | No | 409 |
| DALP-12309 | The custody account needs its external wallet to authorize this request. | The selected custody account is controlled by an external wallet, so the platform cannot sign this operation on its behalf. | Prepare the operation, authorize it with the connected wallet, then finalize the signed artifact. | info | No | 409 |
| DALP-12310 | The external wallet must sign this request. | The selected external custody account has to sign the exact payload the platform prepared for this request. | Connect the selected wallet, sign the returned payload, and send the request again with the signature. | info | No | 409 |
| DALP-12320 | The batch cannot proceed. | The batch's payload, chunk sizing, transaction receipt, or token operation state is not valid, so the batch stopped. | Correct the batch payload or the token permissions it needs, then start the batch again. | info | No | 422 |
| DALP-12324 | A settlement precondition is not met. | The settlement cannot run the requested operation until a precondition it names is satisfied. | Satisfy the precondition, then send the request again. | info | No | 422 |
| DALP-12340 | The token's last administrator cannot be removed. | The change would leave the token without an administrator, so it is refused. | Grant the administrator role to another participant first, then remove this one. | info | No | 409 |
| DALP-12368 | Another network already serves this chain. | Another enabled network in the catalog already serves this chain id. | Disable or remove the network that serves the chain, or give this network a different chain. | info | No | 409 |
| DALP-12371 | The network still serves deployed organizations. | Organizations have systems deployed on this chain, and this change would leave the chain without an enabled network. | Keep an enabled network on the chain while those systems are on it, or enable another network for the chain first. | info | No | 409 |
| DALP-12372 | The network still has RPC upstreams configured. | The network's RPC upstreams were checked against its current chain, and this change would move the network to another chain. | Remove the network's RPC upstreams, make the chain change, then add them again. | info | No | 409 |
| DALP-12373 | Redemption is not available right now. | This redemption cannot be completed at the moment. | Try again later, or contact the issuer of the asset. | info | No | 409 |
| DALP-12377 | The invitation was already accepted. | This invitation was accepted before, so it cannot be accepted again. | Continue with the organization the invitation already joined, or ask an organization owner for a new invitation. | info | No | 409 |
| DALP-12379 | The invitation has expired. | The invitation passed its expiry date before it was accepted. | Ask an organization owner to send a new invitation. | info | No | 403 |
| DALP-12380 | The invitation is no longer open. | The invitation was canceled or declined, so it can no longer be accepted. | Ask an organization owner to send a new invitation. | info | No | 403 |
| DALP-12381 | The inviting organization is archived. | The organization that sent the invitation is archived and accepts no new members. | Ask the organization's owners to restore it, or accept an invitation from another organization. | info | No | 403 |
| DALP-12382 | The organization already holds this national ID. | The organization already has a member with the same national ID as the invitee. | Ask an organization owner to check the existing member's identity before inviting this person again. | info | No | 409 |
| DALP-12383 | The invitation's roles were never authorized. | The invitation grants on-chain roles that no verified wallet authorized. | Ask an organization owner to authorize the invitation's roles with their wallet, or to send a new invitation. | info | No | 412 |
| DALP-12385 | The signer refused to sign this claim. | The signer checked the request against custody, authorization, and approval policy and refused it for a reason that will not clear on retry. data.reason names which. | Read data.reason, resolve the named condition (for example, an unauthorized wallet or a rejected approval), then issue the claim again. | info | No | 409 |
| DALP-12387 | The smart wallet could not be deployed. | A check or step of the deployment refused it, and data.reason names which: the organization runs no account abstraction on this chain, the wallet's controller is another account, no account factory is registered, the signed deadline passed, or the deployment did not land. | Resolve the reason in data.reason, then send the request again. After an expired deadline, request a fresh payload and sign it. | info | No | 409 |
| DALP-12388 | The smart wallet needs a signature from its controlling wallet. | The custody account in data.custodyAccountId is self custody, so the platform holds no key for it. Its wallet has to sign the account factory payload in data.signingPayload before the smart wallet can be deployed. | Sign data.signingPayload with that account's connected wallet, then send the same request again with the signature in externalMessageAuthorization. | info | No | 409 |
| DALP-12389 | This request needs a signature from the selected wallet. | The custody account in data.custodyAccountId is self custody, so the platform holds no key for it. Its wallet has to sign the exact payload in data.signingPayload before this request can continue. | Sign data.signingPayload with that account's connected wallet, then send the same request again with the signature in externalMessageAuthorization. | info | No | 409 |
| DALP-12391 | This token's instrument does not carry the capital this Corporate Action needs. | Share actions such as a bonus issue need share capital, and capital actions such as a split or a buyback need share or unit capital. The token carries neither capability. | Raise this Corporate Action on a share or unit token, or pick a Corporate Action this instrument offers. | info | No | 409 |
| DALP-12393 | Identity recovery has run out of attempts. | This user's recovery failed sixteen times, the most attempts the platform runs for one recovery. | Contact support with the X-Request-Id response header before starting another recovery. | error | No | 409 |
| DALP-12394 | Identity recovery stopped before it finished. | A step of this user's recovery failed, so the recovery stopped before it finished. | Read the recovery status for the step that failed, correct its cause, then execute the recovery again to start a new attempt. | error | No | 409 |
| DALP-14001 | The venue configuration is missing. | The venue exists on-chain but its application configuration is missing. | Repeat creation with the same venue name to restore its configuration. | info | Yes | 409 |
| DALP-14003 | The market listing was refused. | The venue rejected the listing transaction, so no market was listed on-chain. | Read the reason: have each DALP token's issuer enable the hold feature and admit the venue as a hold reserver, bind the venue's escrow vault for a plain ERC-20 token, or review the market sizes, fees, and fee account, then request the listing again. | info | No | 422 |
| DALP-14005 | This token carries no distribution-waterfall feature. | A waterfall allowance names the feature that pulls the pool as its spender, and this token has no such feature attached, so there is nothing to approve. | Grant the allowance on the share class that carries the distribution-waterfall feature, or attach the feature to this token first. | info | No | 404 |
| DALP-14010 | The venue already lists this security under another trading model. | The venue admits each security under one trading model, and a market for this security already runs in a different mode. | List the security in the mode its existing market uses, or delist that market first. A venue admin can also turn the rule off. | info | No | 409 |
| DALP-14011 | The trading venue could not be created. | A creation precondition failed: the organization has no deployed system or venue factory, no wallet is selected as the initial venue admin, or the organization's operations signer is unbound or lacks the system manager role. The factory can also refuse the venue itself. The reason in the response names the failed check. | Resolve the named reason, then create the venue again. For a missing system manager role, a system admin grants it to the account in the response. | info | No | 409 |
| DALP-14012 | This Corporate Action pays a whole multi-class instrument, and this token is not one class of one. | A coordinated distribution splits one pool across the share classes of one instrument, reading the split from the distribution-waterfall feature on the class that holds the pool. This token either belongs to no paired instrument or carries no waterfall. | Raise it on the share class that carries the distribution-waterfall feature. If the instrument was issued outside a paired run, or predates the waterfall, attach the feature first. | info | No | 409 |
| DALP-14013 | The executing wallet cannot fund this pool. | Funding a coordinated distribution pulls the whole pool from the wallet that signs the confirm, so that wallet must hold the pool in the denomination asset and must have approved the distribution-waterfall feature to spend it. The executing wallet does not satisfy both. | Send the pool amount to the executing wallet in the denomination asset, approve the distribution-waterfall feature for at least that amount from the same wallet, then confirm again. | info | No | 409 |
| DALP-14015 | The venue already lists this pair. | A market for this base and quote token pair already exists on the venue, so listing it again would create a duplicate. | Use the existing market, or list a different pair. | info | No | 409 |
| DALP-14016 | The denomination asset refuses to pay this pool into the distribution waterfall. | Funding a coordinated distribution transfers the pool from the executing wallet into the distribution-waterfall feature. A simulated transfer of the denomination asset into the waterfall reverts, so funding would revert too. A denomination that gates recipients by identity refuses a waterfall that has no identity, and a paused denomination refuses every transfer. | Read the contract error in the message. For TransferNotCompliant, call ensurePoolReceiver with the class token on the distribution-waterfall factory as the token's governance, which gives a waterfall deployed before that support its identity. Otherwise clear the denomination's refusal, for example by unpausing it, then preview or confirm again. | info | No | 409 |
| DALP-14017 | The venue refused to admit this private listing. | A private listing must state whether it is sponsored and, where the venue sets admission minimums, the value and share count it makes available at or above them. The field in the response names what is missing or too low. | Complete the named field, or raise the stated value or share count to the minimum in the response, then list again. A venue admin can change the minimums. | info | No | 409 |
| DALP-14018 | The asset type template is not published, so it cannot be unpublished. | The template is still a draft, or your organization already has it unpublished. Unpublishing applies only to a template your organization currently offers for issuance. | Read the template and check isDraft and isPublished. Publish a draft once it is ready; leave an unpublished template as it is. | info | No | 409 |
| DALP-14021 | The payout token cannot be transferred to {ineligibleCount} of the parties that would receive it. | The payout token refuses a transfer from the treasury to one or more holders that would receive a payout: the holder is not verified in its identity registry or its compliance refuses the payout, the payout token's fee recipient cannot receive the transfer fee on that payout, or the treasury cannot pay the payout token's external transfer fee for that many claims. Those holders would fail when they claim. | Read the dividend's denomination eligibility to see which holders are refused and why, then make those holders or the payout token's fee recipient eligible to receive the payout token, fund the treasury's fee-token balance and allowance, or change the dividend's payout token, and declare again. | info | No | 409 |
| DALP-14023 | A published instrument structure uses the asset type template, so it cannot be unpublished. | Your organization offers an instrument structure that issues this template as one of its members, and the structure stays issuable only while every member template is published. data.structures lists each such structure by id and name. | Unpublish the listed structures with PUT /api/v2/settings/asset-type-template-structures/:id/unpublish, then unpublish the template. | info | No | 409 |
| DALP-14030 | This instrument cannot be called before its first call date. | The instrument's metadata names a first call date, and the issuer may call every holder only on or after it. A calendar date (YYYY-MM-DD) starts that day in UTC. A first call date that is neither a calendar date nor a date and time with a UTC offset cannot show the call is open, so it is refused the same way. | Confirm this call on or after the first call date. | info | No | 409 |
| DALP-9072 | Token at {tokenAddress} must expose readable ERC-20 symbol() and decimals() before registration. | External token registration requires ERC-20 metadata so denomination-quoted price feeds can resolve the asset after token creation. | Register a contract that implements ERC-20 metadata, or verify the address and network before retrying. | info | No | 422 |
| DALP-9073 | Denomination asset at {denominationAsset} must expose readable ERC-20 symbol() and decimals() before token creation. | Bond and maturity assets seed a denomination-quoted price feed that reads ERC-20 metadata on-chain after deploy. | Choose a denomination asset that implements ERC-20 metadata, or register the external token with valid ERC-20 metadata before creating the bond. | info | No | 422 |
| DALP-9095 | This person already belongs to this organization. | The organization already has an active member registered under this email address, so a second invitation would create a duplicate membership. | Open the existing member from the participants list to adjust their roles, or send the invitation to a different email address. | info | No | 409 |
| DALP-9175 | The selected template requires additional feature parameters before the token can be created. | The template marks these feature-config params required at deploy time, and the request left them unset or at zero, which the template treats as unset. | Provide a non-zero value for each listed param in the matching featureConfigs entry and resubmit the token creation request. | info | No | 422 |
| DALP-9176 | The selected template requires a conversion window that has not already ended. | The template marks the conversion window required at deploy time, and the requested window end is in the past. The instrument would be expired at creation and could never convert. | Set conversionWindowEnd to a future time in the featureConfigs.conversion entry and resubmit the token creation request. | info | No | 422 |
| DALP-9290 | The conversion feature cannot resolve a usable interest provider. | The conversion feature discovers its interest provider through ERC-165. With both yield features attached it finds two, refuses to auto-select, and every interest-bearing conversion path fails closed after deployment. An explicit provider replaces that discovery, so it must itself be a deployed contract that answers ERC-165 for IConversionInterestProvider and reports the same denomination asset as the conversion. The conversion config is immutable and has no provider setter, so neither case is repairable after creation. | Set featureConfigs.conversion.interestProvider to a deployed interest provider that uses the conversion's denomination asset, or attach only one yield feature and leave the provider unset so discovery resolves it. | info | No | 422 |
| DALP-9291 | The MarkConverted debt method cannot be combined with a yield feature. | MarkConverted records a conversion without moving tokens, so it suits instruments whose token is a receipt and whose principal is held in a separate ledger. Yield features pay out on the token balance, which on such an instrument is not the amount owed. After a conversion it no longer reflects active principal either. | Pick the Burn or Lock debt method, which retire the converted principal and keep the balance accurate, or remove the yield feature from the design. | info | No | 422 |
| DALP-9313 | No Canton participant network is configured. | This deployment has no Canton participant network, so the platform cannot allocate a party or submit a DAML command. | Ask an operator to add a Canton network to the platform configuration, then retry. | info | No | 422 |
| DALP-9314 | The approved Canton command no longer applies. | The DAML command was approved, then the target contract or ledger state changed so the same command cannot settle. | Submit a new command. The existing approval is not reopened. | info | No | 409 |
| DALP-9319 | This custody provider cannot create Canton party wallets. | Canton party wallets require Ed25519 key generation and digest signing. The organization's custody provider does not offer that capability, and the platform does not substitute another provider. | Create the party wallet on an organization whose custody provider supports Canton signing. | info | No | 422 |
| DALP-9321 | The Canton command's validity window closed. | The command's validity window closed while the intent waited for approval, so the platform never sent it to the ledger. | Submit the command again. The expired intent is terminal and its approval is not reopened. | info | No | 410 |
| DALP-9325 | The batch's allocations do not cover its transfer legs exactly. | Every leg of a batch needs both a sender and a receiver side authorized by an allocation, and at least one leg had neither or only one, so no leg executed and the platform released the escrow it had drawn. | Read the uncovered legs and unauthorized sides named in the response, escrow the missing sides, then submit the batch again. | info | No | 409 |
| DALP-9326 | The operation is not available on the selected ledger family. | The request selected a ledger family for which this operation has no serving contract, so the platform stopped before it queried a different ledger. | Select one of the supported ledger families named in the response, then retry the operation. | info | No | 422 |
| DALP-9328 | The Canton network is disabled on this deployment. | The request named a Canton network this deployment is not currently running, so the platform created no intent, recorded no approval, and sent nothing to the ledger. | Ask an operator to enable the Canton network, then submit the request again. Work already accepted stays parked and resumes when the network is enabled. | info | No | 422 |
| DALP-9425 | The system operation requirements were not met. | The target contract could not accept the supplied system input or sender authority. | Check the system addresses and parameters, then use a sender with the required on-chain role. | info | No | 400 |
| DALP-9426 | The system state already conflicts with this operation. | A system role or resource changed before this operation completed, or the requested change is already applied. | Read the current system roles and resource state, then rebuild the request from that state. | info | No | 409 |
| DALP-9427 | The system contract refused the operation. | Contract checks refused the operation after request validation because its authority, address, or state requirement was not met. | Read the target contract state and required roles, correct the failed requirement, then retry. | info | No | 422 |
| DALP-9440 | No blockchain system is available for this organization. | The active organization has no indexed system on the selected network, so the requested system-backed profile or operation does not exist there. | Deploy the organization system or select a network where its system is indexed, then retry. | info | No | 404 |
| DALP-9460 | The conversion window has not opened. | The chain timestamp is before the configured conversion start. | Submit the conversion after windowStart. Check the window returned by the conversion feature. | info | No | 409 |
| DALP-9461 | The conversion window has closed. | The chain timestamp is after the configured conversion end. | Ask the issuer to review the conversion window; retrying the same request cannot reopen it. | info | No | 409 |
| DALP-9462 | A conflicting token feature is already attached. | {{featureName}} cannot be attached while {{conflictingFeatureName}} is attached. | Detach {{conflictingFeatureName}}, or choose a feature that can be combined with {{featureName}}. | info | No | 409 |
| DALP-9463 | The yield feature conflicts with conversion accounting. | The conversion debt method leaves retired principal in holder balances, so this yield feature would pay against retired principal. | Use a token design whose conversion retires principal through burn or lock before adding this yield feature. | info | No | 409 |
| DALP-9464 | Conversion cannot select one interest provider. | Attaching this feature would leave the immutable conversion configuration without one usable interest provider. | Choose a feature combination with exactly one interest provider supported by the conversion configuration. | info | No | 409 |
| DALP-9465 | The feature factory is not installed. | The active system has no factory for the requested token feature. | Install the feature factory on this system, then attach the feature. | info | No | 409 |
| DALP-9466 | The requested feature is not attached. | The token has no attached feature matching this operation. | Read the token features and attach the required feature before calling this operation. | info | No | 409 |
| DALP-9467 | The feature name does not match its address. | The supplied feature address identifies a different feature type. | Use the name and address from the same row returned by the token features endpoint. | info | No | 409 |
| DALP-9468 | The feature projection is behind the chain. | The indexed feature address does not match the feature currently attached on chain. | Wait for the indexer to catch up, read the attached feature again, and retry. | info | Yes | 409 |
| DALP-9469 | The replacement feature address is unchanged. | The requested replacement is already the attached feature address. | Keep the existing feature or supply a different replacement address. | info | No | 409 |
| DALP-9470 | The fixed-yield addon is not installed. | The active system has no fixed-yield addon for this operation. | Install the fixed-yield addon on this system before creating a schedule. | info | No | 409 |
| DALP-9471 | The yield denomination is not indexed. | The schedule denomination asset has no indexed token record. | Register the denomination asset and wait for its token projection before retrying. | info | Yes | 409 |
| DALP-9472 | Yield denomination metadata is missing. | The indexer has not recorded the denomination metadata needed to interpret payout amounts. | Restore denomination metadata indexing, then retry; do not assume token decimals. | info | Yes | 409 |
| DALP-9473 | The fixed-yield deployment is not indexed. | The deployed fixed-yield contract has no corresponding indexed deployment state. | Check the deployment transaction and restore indexer progress before retrying. | info | Yes | 409 |
| DALP-9474 | The yield schedule was not found. | The requested schedule is not available in the active system. | Use a schedule returned by this system and verify its address and network. | info | No | 409 |
| DALP-9475 | The yield schedule belongs to another system. | The schedule is not owned by the system selected for this request. | Select the owning system or use a schedule belonging to the active system. | info | No | 409 |
| DALP-9476 | The schedule token link is not indexed. | The indexer has not linked the yield schedule to its token. | Check the schedule creation transaction and restore indexing before retrying. | info | Yes | 409 |
| DALP-9478 | The token has not matured. | Neither indexed nor live chain state marks the token as matured. | Call the maturity operation when the token is eligible, then redeem. Check maturityDate in this response. | info | No | 409 |
| DALP-9480 | The selected wallet is not the maturity treasury. | This allowance must be approved by the configured treasury wallet. | Select the treasury address returned in this response, then approve the allowance. | info | No | 409 |
| DALP-9481 | The maturity treasury allowance is too small. | The treasury approved {{allowance}} denomination base units; this redemption requires {{required}}. | Have the treasury approve at least the required amount for the maturity feature, then retry. | info | No | 409 |
| DALP-9482 | The holder has insufficient available tokens. | The {{operation}} requests {{requested}} base units from {{holderAddress}}, but only {{available}} are available. | Reduce the amount, fund the holder, or unfreeze enough tokens before retrying. | info | No | 409 |
| DALP-9483 | Token supply changes are paused. | The token is paused, which prevents this {{operation}}. | Have an authorized operator unpause the token before changing its supply. | info | No | 409 |
| DALP-9484 | Mint amounts must be positive. | At least one recipient has a mint amount of zero. | Provide a positive base-unit amount for every recipient. | info | No | 400 |
| DALP-9486 | The token document was not found. | No document matching the requested identifier is available on this token. | Use a document identifier returned by the token document list. | info | No | 404 |
| DALP-9495 | The permit deadline has passed. | The signed permit deadline is earlier than the current chain time. | Create and sign a new permit with a future deadline. | info | No | 422 |
| DALP-9496 | No permit signing wallet is available. | The active organization and chain have no executor wallet available for this permit operation. | Configure an executor wallet for this organization and chain, then retry. | info | No | 409 |
| DALP-9497 | The signed permit was not found. | No signed permit matches this organization, chain, token, and permit identifier. | Use an identifier returned by the permit signing route, or sign a new permit. | info | No | 404 |
| DALP-9498 | The permit was already relayed. | This signed permit was already submitted to the chain. | Read the permit and its transaction result instead of relaying it again. | info | No | 409 |
| DALP-9499 | The permit cannot be relayed. | The signed permit is not pending in a state that accepts relay. | Read the permit state. Sign a new permit if the stored permit expired or was already consumed. | info | No | 409 |
| DALP-9500 | The permit nonce changed. | Another permit reserved the next nonce for this owner before this request could store its signature. | Retry the signing request so the platform can allocate the next available permit nonce. | info | Yes | 409 |
| DALP-9510 | A claim topic with this name already exists. | A claim topic with this name is already registered in the active system. | Use the existing topic, or choose a different name. | info | No | 409 |
| DALP-9524 | The organization has no deployed system on chain {chainId}. | The active organization has no deployed system on its default network. | Deploy the organization system before using system-scoped APIs. | info | No | 404 |
| DALP-9525 | The dividend operation for {dividendId} could not be completed. | The dividend declaration, its snapshot, or its confirmation is not in a state that accepts this operation yet. | Read the dividend and snapshot state, then follow the reported condition before retrying. | error | Yes | 503 |
| DALP-9541 | The approval decision was refused. | The platform four-eyes rules and the policy version the request was raised under decide who may approve and whether the decision is still valid: the maker cannot approve their own request, a role the pinned policy does not name cannot approve, a signature that leaves the policy's approver floor short is recorded against the request rather than admitting it, a borrowed session cannot approve when the pinned policy sets operatorMayApprove to false, a payload that moved invalidates the approval, and an expired request accepts no decision. A policy that names no approving role admits any role the platform has already admitted as an approver. | Read the request again for its current state and row version, and have a distinct operator decide it. | info | No | 409 |
| DALP-9543 | The operations case refused this acknowledgement. | A case that lapsed, that somebody already took, or whose row version moved under the caller accepts no acknowledgement. | Read the cases list again for the current state and row version, then acknowledge the case that is still open. | info | No | 409 |
Operational errors
| DALP Code | Message | Why | Suggested Fix | Severity | Retryable | HTTP Status |
|---|---|---|---|---|---|---|
| DALP-0021 | Deployment workflow reported a terminal failure. | The deployment workflow ended with a Workflow Engine terminal error before the stream could read a typed failed workflow tree. | Open the deployment details or retry only after correcting the workflow failure. Include the request id when contacting support. | error | No | 503 |
| DALP-0031 | Transaction confirmation timeout. | The transaction was submitted but confirmation did not arrive before the timeout. | Check transaction status using the transaction hash and retry only if it was not confirmed. | warning | Yes | 504 |
| DALP-0262 | Multiple active claims found for topic {topicId} on identity {identityAddress}. | The platform found more than one active, non-revoked claim for the same topic on this identity contract. Each topic should have at most one active claim, so this state indicates a data integrity issue the platform cannot resolve automatically. | Contact support with the request id and the identity address. The platform team will audit the duplicate claims and restore the expected single-claim state for this topic. | error | No | 500 |
| DALP-0321 | Declared file size does not match actual file size in storage. | After the upload completed, the platform retrieved the stored object and found its byte length differs from the fileSize value supplied in the confirm-upload request. The orphaned object was removed from storage. | Re-upload the file and submit a confirm-upload request with the exact byte length of the file as reported by your file system. | error | No | 500 |
| DALP-0325 | Failed to create document record. | The platform inserted the document metadata into the database but the insert returned no row, indicating a persistence failure. The orphaned object was removed from storage to avoid an inconsistent state. | Retry the confirm-upload request. If the error recurs, contact support with the request id and the object key. | error | No | 500 |
| DALP-0351 | Bond not yet indexed for this token; retry after the indexer processes the bond initialization. | The indexer has not projected a denomination asset for the legacy bond. | Wait for the bond initialization block to be indexed, then retry. | error | Yes | 404 |
| DALP-0635 | Gas requirement computation failed for this chain. | The chain has an undefined operations budget, or its pending base fee fell below the configured floor. | Reach out to support with the request id; this is a server-side configuration issue and is not user-correctable. | error | No | 503 |
| DALP-0673 | Custody credentials for this organization are unavailable. | The organization's custody record, secret slot, or provider configuration is missing or unreadable, and custody operations fail closed rather than substituting another provider. | Contact support with the request id so an operator can restore the organization's custody configuration. | error | No | 500 |
| DALP-12037 | Wallet verification is at capacity. | Wallet verification admission is full, so the platform stored nothing. The same request can succeed later without any change. | Wait the number of seconds in data.retryAfterSeconds, then send the request again. | error | Yes | 503 |
| DALP-12079 | The asset was already deployed, but the platform could not recover its address. | The creation reverted because the access manager for this asset exists already, which means an earlier attempt deployed it. Recovery reads that earlier asset back so the request can answer with it, and that read found nothing to return. | Look the asset up by name and symbol in the asset list. Contact support with the request id if it is not there. | error | No | 422 |
| DALP-12084 | The price update did not complete. | The workflow that writes the new price to the asset's feed stopped before the feed was updated. The recorded price is the one that was there before the request. | Read the asset's current price, then submit the update again. | error | No | 422 |
| DALP-12085 | The chain this operation targets could not be reached. | The operation needs the chain the asset lives on, either to resolve its configuration or to read state the next step depends on, and that chain answered with neither. | Check that the network is configured and reachable, then submit the operation again. | error | No | 422 |
| DALP-12086 | The transaction landed but its receipt does not describe the result. | The platform reads the outcome of a token write out of the transaction receipt: the hash, the block, and the event the step emits. One of them is absent, so the platform cannot say what the write produced. | Check the asset's current on-chain state before submitting the operation again, and send the request id to support if the state does not explain the outcome. | error | No | 422 |
| DALP-12088 | Whether this token write completed could not be established. | The write was submitted and the platform stopped trying to resolve what became of it. It may still complete, or may already have completed; nothing observed proves it dead. | Do not resubmit. Verify the asset's on-chain state, and send the request id to support if it stays unresolved. | error | No | 422 |
| DALP-12089 | The operation could not pause for the wallet to be funded. | When a wallet cannot pay for its next transaction the operation pauses and records a funding requirement against the organization. Recording that requirement failed, so the operation stopped instead of waiting. | Fund the wallet named in the message, then submit the operation again. | error | No | 422 |
| DALP-12090 | A claim this asset needs could not be issued. | A new asset is issued the identity claims its configuration implies, each as its own step. One of those steps stopped for good, so the asset exists without that claim. | Issue the missing claim on the asset's identity, then continue. Send the request id to support if issuing it fails the same way. | error | No | 422 |
| DALP-12091 | The token workflow stopped for good. | A step in the workflow failed in a way none of the named terminal conditions covers, so the operation cannot continue and will not be retried. | Read the asset's current state to see how far the operation got, then send the request id to support. | error | No | 422 |
| DALP-12107 | The party write outcome is unknown. | The queue may have accepted this write, but its final outcome could not be confirmed. | Look up the transaction request before taking further action. Do not submit a replacement write under a new idempotency key. | error | No | 503 |
| DALP-12108 | The compliance write outcome is unknown. | The queue may have accepted this compliance write, but its final outcome could not be confirmed. | Look up the transaction request before taking further action. Do not submit a replacement write under a new idempotency key. | error | No | 503 |
| DALP-12109 | The smart-wallet write outcome is unknown. | The queue may have accepted this wallet write, but its final outcome could not be confirmed. | Look up the transaction request before taking further action. Do not submit a replacement write under a new idempotency key. | error | No | 503 |
| DALP-12297 | The requested network is disabled. | The network the request named is configured but disabled, so the platform does not serve it. | Choose an enabled network, or ask an administrator to enable this one. | error | No | 503 |
| DALP-12298 | The platform could not use this network's configuration. | The platform could not use the configuration of the network this request needs. | Contact support with the X-Request-Id response header so an operator can correct the network configuration. | error | No | 503 |
| DALP-12299 | The network's configured chain is not supported. | The network the request resolved to names a built-in chain the platform does not support. | Ask an administrator to configure a supported chain or a custom chain definition for this network. | error | No | 400 |
| DALP-12302 | Every network for this executor chain is disabled. | The chain the smart-wallet executor was asked to use has configured networks, but all of them are disabled. | Ask an administrator to enable a network for this chain, or select another chain. | error | No | 503 |
| DALP-12303 | The platform could not read the executor network's configuration. | The network configuration the smart-wallet executor needs could not be decoded. | Contact support with the X-Request-Id response header so an operator can correct the network configuration. | error | No | 503 |
| DALP-12312 | The completed transaction returned no result for this route. | The transaction completed, but the route could not read back the data its response needs. | Read the transaction request to confirm its outcome, then read the resource it changed. Contact support with the X-Request-Id response header if the data stays missing. | error | No | 503 |
| DALP-12313 | The organization's submission signer is not bound. | The organization's deployment has no managed signer bound for this system and chain, so the platform cannot submit the operation. | Contact support with the X-Request-Id response header so an operator can repair the organization's signer binding. | error | Yes | 404 |
| DALP-12316 | The organization's signer does not match its bound wallet. | The wallet the signing provider returns is not the wallet the organization's signer binding records. | Contact support with the X-Request-Id response header so an operator can repair the organization's signer binding. | error | No | 409 |
| DALP-12322 | The custody account store returned an inconsistent result. | The custody account store did not return a row this request requires. | Contact support with the X-Request-Id response header. | error | No | 500 |
| DALP-12331 | The indexer is still catching up on this chain. | The indexer for this chain is rebuilding, and the caller asked to be told instead of waiting while it catches up. | Retry after the number of seconds in data.retryAfterSeconds. | info | Yes | 503 |
| DALP-12335 | The ballot is waiting on a custody approval. | The platform parked signing this ballot until the custody approval it needs is granted. | Approve the pending custody request, then send the ballot again. | info | No | 409 |
| DALP-12367 | The order placement is still in flight. | A request with this idempotency key has claimed the placement, but its order is not available yet. | Retry the unchanged request with the same idempotency key after the first placement completes. | info | Yes | 409 |
| DALP-12374 | The venue signer is unavailable. | The venue could not read or verify the managed signing identity needed for this operation. | Retry after custody and network services recover. If the problem persists, ask a venue operator to check the signer configuration. | error | Yes | 503 |
| DALP-14002 | The venue deployment is still being indexed. | The factory state or venue creation transaction cannot be confirmed yet. | Retry the same venue creation request after the chain and indexer are available. | error | Yes | 503 |
| DALP-14004 | The market listing outcome is not confirmed. | The listing request may have reached the chain, but its outcome cannot be confirmed yet. | Check the market list for this venue and token pair before sending another listing request. | error | No | 503 |
| DALP-14006 | The distribution-waterfall feature did not answer which asset it pays in. | The allowance is granted on the pool's denomination asset, which is read from the feature on chain. That read returned no asset, so approving anything now risks approving the wrong token. | Restore chain access and confirm the feature is deployed, then grant the allowance again. | error | Yes | 503 |
| DALP-9080 | Convert is settling this holder's accrued-interest backlog to target tokens; re-submit to finish the conversion. | Convertible-interest settlement is still advancing through bounded on-chain batches. | Wait for the accepted settlement batch, then retry the conversion with the same idempotency key. | error | Yes | 409 |
| DALP-9195 | Another custody operation is still in progress. | The platform could not acquire the organization's custody rotation lock before the wait window ended. | Wait for the active custody operation to finish, then retry the rotation. | error | Yes | 503 |
| DALP-9421 | The stored exchange-rate feed could not be read. | A feed row in the platform database does not match the shape the read expects, so the platform stopped rather than publish a rate it cannot stand behind. | Repair the named feed row in the database, then send the request again. | error | No | 500 |
| DALP-9429 | The system operation outcome is unknown. | Recovery stopped before the platform could confirm whether the underlying write completed. | Do not resubmit the operation. Verify its final on-chain state before taking further action. | error | No | 503 |
| DALP-9477 | Maturity state is not indexed. | The maturity feature state required for this operation is absent from the index. | Check the feature deployment and restore indexer progress before retrying. | info | Yes | 503 |
| DALP-9479 | The maturity treasury has not been classified. | The indexer has not determined whether the configured treasury is a wallet or a contract. | Restore treasury classification indexing before redeeming. | info | Yes | 503 |
| DALP-9501 | The permit feature is unavailable. | The permit feature state has not finished indexing, or its declared signing domain does not match the indexed one. | Wait for the permit feature state to finish indexing, then retry. | info | Yes | 503 |
| DALP-9532 | The request deadline expired. | The request ran past the deadline the platform gives one request, so the platform stopped the work. The operation that request started may still be running. | Check the status of the operation before you submit the request again, and let the Retry-After interval pass first. | warning | No | 504 |
Dependency errors
| DALP Code | Message | Why | Suggested Fix | Severity | Retryable | HTTP Status |
|---|---|---|---|---|---|---|
| DALP-0009 | Session resolution failed. | Platform API could not resolve the authenticated session from the request headers. | Retry with a fresh session or API key. If the problem continues, contact support with the request id. | error | Yes | 503 |
| DALP-0012 | Transaction provider read failed. | The configured chain RPC provider could not read transaction state for this request. | Retry after a short backoff. If the problem continues, contact support with the request id. | error | Yes | 503 |
| DALP-0020 | Deployment stream polling failed. | The deployment event stream could not read the latest workflow status from the Workflow Engine. | Reconnect to the stream or poll deployment status after a short backoff. If it continues, contact support with the request id. | error | Yes | 503 |
| DALP-0045 | Ledger Index reindex admin is unreachable. | Platform API could not contact the Ledger Index Indexing Pipeline service that starts blockchain reindex jobs. | Retry after a short backoff. If the problem continues, contact support with the request id. | error | Yes | 503 |
| DALP-0076 | Denomination asset pending indexing. | The fixed-yield operation needs the denomination asset row, but the indexer has not exposed it yet. | Retry after indexing catches up. | error | Yes | 503 |
| DALP-0082 | Service temporarily unavailable. | A required backend service is temporarily unavailable. | Retry after a short backoff. If the problem continues, contact support with the request id. | error | Yes | 503 |
| DALP-0083 | Indexer data temporarily incomplete. | Platform API is reading from an indexer schema that is still rolling out or reindexing. | Retry after the indexer rollout completes. If the problem continues, contact support with the request id. | warning | Yes | 503 |
| DALP-0115 | The v1 token access change returned no synchronous result. | The frozen v1 mutation did not produce a synchronous result. | Retry with the same idempotency key or inspect the transaction request status. | error | Yes | 503 |
| DALP-0151 | The workflow engine call failed. | A call to the workflow execution service returned an error that does not map to a more specific error code. The service may be temporarily unavailable or returned an unexpected response. | Retry the request. If the problem persists, contact support with the request ID. | error | Yes | 503 |
| DALP-0330 | Fixed-treasury-yield feature state not yet indexed for this token. | The platform looked up the fixed-treasury-yield feature row (denomination asset and treasury address) for this token but found no indexed record, or the record contains zero-address values. The platform's index has not yet processed the feature initialization event. | Retry after a short delay to allow the platform's index to process the feature initialization. If the error persists, contact support with the request ID. | error | Yes | 503 |
| DALP-0333 | Token features for {featureName} are not available. | The platform could not read the feature state for this token from the chain or the index. The chain node or a downstream data source returned an error. | Retry after a short delay. If the error persists, contact support with the request ID. | error | Yes | 503 |
| DALP-0339 | Indexed data validation failed. | A field in the indexed token or feature inventory does not match the expected format. | Repair or reindex the token or feature inventory projection, then retry the request. | error | No | 500 |
| DALP-0431 | Could not resolve the created XvP settlement from the indexer after retries. | The XvP create route submitted the settlement creation transaction and confirmed it on-chain, but the indexer did not produce the settlement row within the retry window. The indexed settlement is required to return the settlement ID and state to the caller. | Retry the request. If the settlement ID is needed immediately, query the indexer directly after a short delay. Contact support with the request ID if the problem persists. | error | Yes | 503 |
| DALP-0441 | Workflow Engine workflow call conflicted with the current workflow state. | A Workflow Engine endpoint returned HTTP 409 because the downstream workflow state did not allow this call at this time. | Refresh the resource or deployment status, wait for the active workflow step to finish, then retry if the operation is still valid. | info | No | 409 |
| DALP-0447 | Transaction queue could not complete the operation. | The transaction failed on-chain without a revert reason the API can decode, the sending smart wallet cannot fund it, or the queue rejected its input. | Check the operation input, the current contract and token state, and the funds of the sending wallet, then retry with a new idempotency key. | info | No | 422 |
| DALP-0448 | Transaction queue confirmation timed out. | The transaction queue did not observe the queued transaction confirmation before its timeout window expired. | Check the transaction status before retrying so you do not submit a duplicate operation. | warning | Yes | 504 |
| DALP-0496 | Compliance provider rejected applicant creation. | The provider applicant or monitored-subject creation call failed before DALP could persist the subject mapping. | Verify provider credentials and the submitted subject fields, then retry applicant creation. | error | No | 502 |
| DALP-0525 | Compliance provider rejected transaction registration. | The provider transaction-registration call (Sumsub KYT) failed before DALP could persist the transaction-id mapping. | Verify provider credentials and the submitted transaction fields, then retry transaction registration. | error | No | 502 |
| DALP-0536 | The permission check could not be completed. | The authentication provider could not evaluate whether the caller holds the permission this route requires, so the platform refused the request rather than admitting or denying it on a guess. | Retry the request. If the failure continues, ask your operator to confirm the authentication provider is reachable. | error | Yes | 503 |
| DALP-0656 | Indexer v_bond_status view has not yet computed a row for the attached maturity-redemption feature. | The /v2/tokens/:assetId/treasury/health route reads the indexed v_bond_status view for the authoritative denominationRequired ceiling driving the redemption approval. The maturity-redemption feature is attached but the view has not landed a row yet, so collapsing the missing required amount to zero would render a false green badge while the indexer catches up. | Retry after the indexer catches up to the latest idxr_token_bonds insert. If the failure persists, verify the indexer is making forward progress on the active chain. | error | Yes | 503 |
| DALP-0660 | Identity provider verification is temporarily unavailable. | Platform API could not reach the identity provider to complete the verification for this signing request. | Retry after a short backoff; if it persists, contact support with the request id. | error | Yes | 503 |
| DALP-0717 | A dependency of this route is unavailable. | A dependency this route needs did not answer. | Retry; the request was not applied. | error | Yes | 503 |
| DALP-0732 | The returns snapshot could not be taken. | The snapshot reads every position in one transaction and lost that read to concurrent writers twice, so it stopped rather than answer a torn total. | Retry after a short backoff. | error | Yes | 503 |
| DALP-0735 | Governance state is temporarily unavailable. | Governance state could not be read from the chain or from its indexed projection. | Retry after a short backoff. If the problem continues, contact support with the request id. | error | Yes | 503 |
| DALP-0737 | Portfolio returns are temporarily unavailable. | A return amount has incomplete denomination metadata, its denomination asset has no price, or no configured FX path connects its price currency to the organization's base currency. The response data names the currencies and reason. | For denomination-metadata-missing, wait for the denomination token to index. For denomination-unpriced, publish a price for the denomination asset. For fx-path-unavailable, configure a feed path from priceCurrency to baseCurrency, then retry after pricing updates. | error | Yes | 503 |
| DALP-12032 | The indexed state this claim needs is not recorded yet. | The platform authorizes a token claim against indexed state: the token's on-chain identity, the claim registries of the active system, and the acting wallet's active registration in the identity registry. The indexer has not recorded one of them yet. data.reason names which. | Wait for the indexer to catch up, then retry. If it does not clear, check that the token identity and the issuer registration exist on chain. | error | Yes | 503 |
| DALP-12038 | Wallet verification could not complete. | A service wallet verification depends on, the wallet credential store or the identity provider, did not answer, so the platform stored nothing. | Retry after a short backoff. If it continues, contact support with the request id. | error | Yes | 503 |
| DALP-12073 | Stored workflow progress is malformed. | The saved workflow progress does not match a supported version, so Corporate Action recovery cannot determine which chunks completed. | Inspect and repair the workflow execution status progress value before retrying the Corporate Action operation. | error | No | 500 |
| DALP-12074 | The transaction succeeded on-chain, but its indexed data is not ready. | The indexer did not finish projecting the transaction's block before the request deadline. The write has already succeeded and must not be submitted again. | Check the transaction request using transactionId. Ask an operator to inspect indexer errors for chainId at or before blockNumber and restore projection progress, then repeat the read. Do not resubmit the mutation. | error | Yes | 504 |
| DALP-12101 | Mark refresh dependency did not answer. | The avatar store, the ENS resolver, or object storage did not answer, so the platform stored nothing and the mark is unchanged. | Retry the refresh after a short delay. | error | Yes | 503 |
| DALP-12103 | Party service temporarily unavailable. | A service the party domain depends on did not answer. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
| DALP-12104 | Transaction dependency temporarily unavailable. | The transaction request could not read its caller scope or a required queue dependency. | Retry the same request after a short backoff. Do not submit a replacement transaction. | error | Yes | 503 |
| DALP-12105 | Transaction outcome not yet known. | The transaction may have settled, but the platform could not read its final state. | Read the transaction request status using its transaction id. Do not submit a replacement payment. | error | No | 503 |
| DALP-12106 | Portfolio write outcome not yet known. | The portfolio write may have reached the chain, but its final outcome could not be read. | Read the transaction request status using its id. Do not submit a replacement write. | error | No | 503 |
| DALP-12134 | Object storage did not complete the profile image operation. | Object storage did not answer the presign, read, or delete for the profile image objects. | Restore object storage availability, then send the same image request again. | error | Yes | 503 |
| DALP-12146 | The order was not signed. | The custody provider did not return a signature for the order, or the signature needs a custody approval first. | Approve any pending custody request for the wallet, then sign the order again. | error | Yes | 503 |
| DALP-12148 | The database is temporarily unavailable. | The platform could not complete a database query required for this request. | Retry the request. If the failure continues, contact support with the request id. | error | Yes | 503 |
| DALP-12194 | A service this request depends on returned an answer the platform could not use. | A service this operation depends on answered, but the platform could not use the answer. The failing dependency publishes no error entry of its own, so this general 502 stands in for it. | Retry after a short delay. If it continues, contact support with the request id. | error | Yes | 502 |
| DALP-12233 | A required Canton capability is unavailable. | The Canton participant or a service it depends on did not provide a capability this operation needs, so the platform did not complete the request. | Retry later. If the refusal persists, ask an operator to restore the Canton participant connection. | error | Yes | 503 |
| DALP-12240 | The feed directory for this system is not available. | The selected network has no indexed feed directory for this system, or the directory could not be read. | Confirm the system bootstrap installed the feed directory and the indexer has caught up, then retry. | error | Yes | 503 |
| DALP-12248 | KYC data temporarily unavailable. | A store the KYC or user profile route reads did not answer, so the route could not complete. data.dependency names the store. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header and data.dependency. | error | Yes | 503 |
| DALP-12249 | Compliance service temporarily unavailable. | A service the compliance route depends on did not answer: the compliance provider, the secret store that holds its credentials, or the network catalog. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
| DALP-12250 | Platform dependency temporarily unavailable. | A dependency required to complete this platform request did not answer. | Retry after a short backoff. If it persists, contact support with the request ID. | error | Yes | 503 |
| DALP-12258 | The authentication store did not answer. | A read or write against the session, account security, or API key store did not complete, or the store returned a row the account contract refuses. | Retry after a short wait. If the failure persists, contact support with the request id. | error | Yes | 503 |
| DALP-12268 | Compliance authorization temporarily unavailable. | The custody account directory did not resolve the executor needed to check this caller's compliance role. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
| DALP-12269 | Account-abstraction status temporarily unavailable. | The indexed store or chain behind this gas-sponsorship read could not be reached. | Retry the read after a short backoff. If the problem continues, contact support with the request id. | error | Yes | 503 |
| DALP-12290 | The claim-topic exclusion policy is temporarily unavailable. | The store that holds the claim-topic exclusion policy did not answer, so the request could not complete. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
| DALP-12300 | The blockchain node did not answer. | The blockchain RPC endpoint the network uses did not complete the read this request needs. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
| DALP-12304 | The executor network's node did not answer. | The RPC endpoint or account factory of the smart-wallet executor's network failed during this request. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
| DALP-12307 | The organization's network settings are temporarily unavailable. | The platform could not load the organization's network configuration for this request. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
| DALP-12314 | The organization's submission signer could not be read. | The platform could not read the organization's managed signer binding for this system and chain. | Retry the same operation after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
| DALP-12315 | The organization's signing provider did not answer. | The signing provider bound to the organization could not resolve the wallet that submits this operation. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
| DALP-12317 | The transaction processor's dependency did not answer. | A service the transaction processor needs failed while it handled this operation. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
| DALP-12326 | A settlement dependency is temporarily unavailable. | A service the settlement operation needs did not answer, so the operation did not run. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
| DALP-12332 | Platform asset storage is temporarily unavailable. | The object storage that holds platform assets did not answer. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
| DALP-12334 | The organization's system scope is temporarily unavailable. | The platform could not load the active organization's system and identity registry scope. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
| DALP-12336 | The permission check could not run. | The authentication provider did not answer while the platform checked whether the caller may make this request, so the request did not run. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
| DALP-12337 | The token's claim topics are temporarily unavailable. | The store that holds the token's claim topics did not answer, so the request could not complete. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
| DALP-12338 | Pending identity registrations are temporarily unavailable. | The store that holds pending identity registrations did not answer, so the request could not complete. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
| DALP-12341 | The participant for this role change could not be resolved. | The platform could not resolve the participant or wallet the role change names. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
| DALP-12344 | The token deployment's progress is temporarily unavailable. | The store that records token deployments did not answer, so the deployment's progress could not be read. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
| DALP-12346 | A token deployment step could not be read. | The platform could not read a step of the token deployment while streaming its progress. | Reconnect to the deployment stream after a short backoff. | error | Yes | 503 |
| DALP-12347 | The deployed token could not be read back. | The token was deployed, but its indexed record could not be read back to complete the response. | Read the token after a short delay. Do not deploy it again. | error | Yes | 503 |
| DALP-12354 | The transfer check is temporarily unavailable. | The platform could not simulate the transfer on chain, so it cannot say whether the transfer would succeed. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
| DALP-12355 | The claim could not be issued right now. | A service the claim issuance needs did not answer, so the claim was not issued. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
| DALP-12356 | The conversion feature could not be read. | The platform could not read the conversion feature's on-chain state for this request. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
| DALP-12358 | The denomination token's metadata could not be read. | The platform could not read the denomination token's metadata on chain. | Retry after a short backoff. If the problem continues, check that the denomination address is a token contract. | error | Yes | 503 |
| DALP-12360 | The token's access control could not be resolved. | The platform could not resolve the token contract or access manager this change targets. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
| DALP-12364 | The indexer could not read its progress. | The indexer listener could not read its persisted block-progress checkpoint, so the data this route reads is not confirmed current. | Retry after a short backoff. If the problem continues, contact support with the X-Request-Id response header. | error | Yes | 503 |
| DALP-12365 | Platform write outcome not yet known. | The platform write may have been recorded or reached the chain, but its outcome could not be read. | When transactionId is present, read that transaction request; when it is absent, no request could be confirmed. Read the held roles before another write. Resending the same role set under the same idempotency key reuses the earlier request only while the held roles are unchanged; after they change, it plans only the changes still missing and can open a new request. | error | No | 503 |
| DALP-13001 | Permit information cannot be read: {operation} failed ({reason}). | The indexed domain separator is absent, or the permit feature returned a terminal read failure. | Check the permit feature and indexer on the selected network; include the request ID when reporting the failure. | error | No | 422 |
| DALP-14022 | Indexed holdings data validation failed. | A field in an indexed holdings, price, or token-metadata row does not match the expected format. | Repair or reindex the affected holdings, price, or token-metadata projection, then retry the request. | error | No | 500 |
| DALP-9079 | Couldn't read ERC-20 metadata because the RPC endpoint was temporarily unavailable. | The preflight reads symbol() and decimals() live from the chain; that RPC request failed to reach a usable response (connection error, timeout, or rate limit) rather than the contract reverting. | Retry after the Retry-After interval. If it persists, check the network's RPC endpoint health. | error | Yes | 503 |
| DALP-9087 | The wallet balance is too low to cover this transaction's gas. | The network rejected the transaction because the signing wallet does not hold enough of the network's gas token to pay for it: the gas the transaction needs multiplied by the gas price, plus any value it sends. On a network where gas is not free, transactions from this wallet stop here until someone tops it up. | Send the network's gas token to the wallet, then submit the transaction again. The error data carries shortfallWei (the smallest amount to add), recommendedTotalWei (a buffered target that also covers the next few operations), the wallet address, the chainId, and the gas tokenSymbol to send. | error | Yes | 422 |
| DALP-9091 | The organization's bundler wallet cannot cover this operation. | The bundler wallet that submits this organization's account abstraction operations does not hold enough of the network's gas token. The operation waited for funding and reached its inclusion timeout, so it was not sent to the network. | Send the network's gas token to the bundler wallet, then submit the operation again. The error data carries the bundler address, the chainId, and requiredWei, the amount the bundler asked for. The organization dashboard shows the same address with a fund action. | error | Yes | 422 |
| DALP-9166 | The voting-power operation could not be completed. | Voting power is not indexed for the token, the voting wallet is not active in a recognized identity registry, or the delegation signature does not verify. | Wait for the voting-power feature to be indexed, register the voting wallet, or create a fresh delegation signature, then retry. | error | Yes | 503 |
| DALP-9244 | The tenant wallet could not be resolved. | The request could not resolve the tenant wallet required for this operation. | Verify the participant wallet assignment and wallet service availability, then retry. | error | Yes | 503 |
| DALP-9253 | The system projection is temporarily unavailable. | The indexed system projection could not be resolved for this request. | Retry after the indexer catches up or verify the organization system setting. | error | Yes | 503 |
| DALP-9259 | Token data is temporarily unavailable. | The indexed token projection could not be read for this request. | Retry after the indexer database is available; if the failure persists, inspect its query health. | error | Yes | 503 |
| DALP-9260 | Portfolio data is temporarily unavailable. | The indexed portfolio data required by this endpoint could not be read or persisted. | Retry after the indexer database is available; if the failure persists, inspect its query health. | error | Yes | 503 |
| DALP-9266 | Token feature data is temporarily unavailable. | The token-feature data required by this endpoint could not be read or persisted. | Retry after the token database is available; if the failure persists, inspect its query health. | error | Yes | 503 |
| DALP-9267 | The token write could not be persisted. | A persistence operation required by the token mutation failed. | Retry after the token database is available; if the failure persists, inspect its write health. | error | Yes | 503 |
| DALP-9288 | Token factory registry is not ready for this system. | The active system has no indexed token-factory registry address, so the token list cannot authorize which factories belong to the system. | Wait for the system token-factory registry to index, then retry the request. | error | Yes | 503 |
| DALP-9318 | Canton command submission failed. | The platform accepted the command, then submission stopped before the ledger settled it. | Inspect the submission status, then retry with the same submission id when the failure is retryable. | error | No | 500 |
| DALP-9320 | The reporting source could not be read. | A source the report derives from did not answer, so the platform rendered no section rather than an empty one. A period with no activity is a nil return and never reports this error. | Repeat the request. If it keeps failing, check the platform database and Ledger Index health. | error | Yes | 503 |
| DALP-9441 | Blockchain authorization state is unavailable. | The platform could not load the indexed wallet or account-abstraction state needed to authorize the request. | Retry after the database projections recover. If the failure continues, contact support with the request id. | error | Yes | 503 |
| DALP-9502 | The permit signature could not be produced. | The configured custody signer did not complete the permit signing request. | Restore the custody signer or complete its pending approval, then retry. | error | Yes | 503 |
| DALP-9505 | Permit storage is unavailable. | The platform could not read or save the permit state required by this operation. | Restore permit storage, then retry without changing the request scope. | error | Yes | 503 |
| DALP-9506 | The token denomination is not indexed. | The symbol and decimals needed to encode the submitted amount are not indexed for the token yet. | Wait for the token symbol and decimals to be indexed, then retry with the same idempotency key. | error | Yes | 503 |
| DALP-9526 | Transaction was dead-lettered before it could settle. | The transaction queue moved the transaction to DEAD_LETTER: it failed with no revert the platform could decode, so no automatic retry can complete it. | Read the transaction status for the terminal failure detail, correct the request or the state it depends on, then submit again with a new idempotency key. An operator can force-retry the dead-lettered transaction once the cause is repaired. | error | No | 422 |
Contract errors surfaced at the API
| DALP Code | Message | Why | Suggested Fix | Severity | Retryable | HTTP Status |
|---|---|---|---|---|---|---|
| DALP-12366 | A role write failed on chain. | A role write failed on chain. In a role set no earlier write is undone; in a role batch the calls sent before it stay applied on a signing-wallet executor. | Read the transaction request by id and the held roles, then send only the changes still missing. | info | No | 422 |
Unclassified errors
| DALP Code | Message | Why | Suggested Fix | Severity | Retryable | HTTP Status |
|---|---|---|---|---|---|---|
| DALP-0084 | The platform could not complete this request. | An unexpected failure occurred after the request passed validation. | Retry once. If it continues, contact support with the request id. | error | No | 500 |