This page lists the 52 errors the Platform API can return with a code from DALP-12200 to DALP-12299. Match the id in the error envelope to the DALP Code column, then read Retryable and Suggested Fix. The Platform API error reference explains each column, including Severity, and the DALP error index lists the page for every code range.
DALP Code | Machine name | Category | Message | Why | Suggested Fix | Severity | Retryable | HTTP Status |
|---|---|---|---|---|---|---|---|---|
DALP-12230 | CANTON_ | domain | 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 | CANTON_ | domain | 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. A compensation, or a submission that groups others, carries no approval to decide and answers the same way. | Read the submission and keep its recorded approval decision. | info | No | 409 |
DALP-12232 | CANTON_ | permission | You may not decide this Canton command. | Only an organisation owner or a platform administrator can decide a Canton command intent. An instrument write also needs a party that holds the instrument role the write requires. | Ask an organisation owner or a platform administrator to record the decision. For an instrument write, submit as a party that holds the required role. | info | No | 403 |
DALP-12233 | CANTON_ | dependency | 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-12234 | CANTON_ | domain | The Canton participant rejected the command. | The Canton participant rejected the command, the custody provider refused to sign it, or the command named a target it does not apply to, so the ledger did not change. | Correct the command or its target, then submit it again. If the custody provider refused to sign, ask its approver why before you resubmit. | info | No | 422 |
DALP-12235 | CANTON_ | client | 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-12240 | FEED_ | dependency | 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-12241 | FEED_ADDON_NOT_INSTALLED | domain | 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 price resolver or feed factory add-on this operation uses on this system, then send the request again. | info | No | 409 |
DALP-12242 | FEED_ | permission | The acting wallet cannot manage feeds on this system. | Feed writes need the feeds manager role on the system and a managed signing account for the organisation on this chain. The executing wallet does not hold the role, or the organisation has no such account. | Ask a system administrator to grant the feeds manager role to the executing wallet, or provision the organisation's managed signing account on this chain, then retry. | info | No | 403 |
DALP-12243 | FEED_ | permission | The feed update was not signed. | The custody policy for the issuer key refused to sign this feed update, no custody signer is recorded for the feed, or the feed does not trust the submitting identity as an issuer for its topic. | Check the custody policy and custody signer for the issuer key, or submit the update with an identity that the policy allows to sign and the feed trusts as an issuer for its topic. | info | No | 403 |
DALP-12244 | FEED_ | domain | 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-12245 | FEED_ | client | 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 | FEED_ | client | 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 | EXCHANGE_ | client | 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 that GET /api/v2/exchange-rates/supported-currencies returns, or add an exchange-rate feed for the currency on this network. | info | No | 422 |
DALP-12248 | compliance. | dependency | 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. | dependency | Compliance service temporarily unavailable. | A service the compliance route depends on did not answer: the compliance provider, the secret store that holds its credentials, the network catalog, a KYC store write, or the claim-topic exclusion policy read. | 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 | 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-12251 | platform. | client | 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-12252 | platform. | permission | Platform access denied. | The caller cannot perform this platform operation. | Sign in and complete any wallet verification the operation asks for, or ask whoever grants the role it needs, then retry. An organization owner grants the owner role that changing an organization's members or their roles needs. Removing a member also needs the identityManager role on your wallet. | info | No | 403 |
DALP-12253 | wire. | auth | 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-12255 | compliance. | permission | 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-12257 | CUSTODY_ | client | Custody account not found. | No custody account or custody lifecycle request visible to the caller in the active organisation matches this identifier. | Refresh the active organization's account list and choose an account returned there. | info | No | 404 |
DALP-12258 | AUTH_STORE_UNAVAILABLE | dependency | The authentication store did not answer. | A read or write against the session, account security, or API key store did not complete. | Retry after a short wait. If the failure persists, contact support with the request id. | error | Yes | 503 |
DALP-12259 | SESSION_ | permission | 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-12260 | USER_ | client | 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 | MULTISIG_NOT_ENABLED | client | 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-12262 | TRADE_ | permission | 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. The reversal is also refused when another executor already claimed the bust, a reversal leg did not settle, or a bust escrow, parked fill or queue record could not be read. | 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-12263 | MARKET_CALENDAR_INVALID | client | The instrument 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 instrument schedules a pre-open. The calendar is also refused when an edit or delete targets a past venue closure or a date with no closure, when a move lands on a date that already has one, or when a collection window overlaps a session that already started. | Use an IANA timezone and session times with pre-open at or before open and open before close. On a private continuous instrument, leave pre-open empty for every weekday and every open exception, then submit the calendar again. Edit or delete only a venue closure that falls on the current day or a later one. | info | No | 422 |
DALP-12264 | MARKET_FIELD_IMMUTABLE | client | The instrument setting cannot be changed. | A listed instrument keeps its matching mode, private flag, sponsorship, reference price, admission figures and go-live schedule. A delisted one keeps its maturity cut-off and its valuation and reference prices. An instrument's valuation is fixed once its first auction runs. A valuation or reference price off the tick grid, a base-token price designation on an instrument with no system address, and a listing approval this operator no longer holds are refused too. | Keep those settings unchanged, or list a new instrument with the settings you need. Send valuation and reference prices on the instrument's tick grid. | info | No | 422 |
DALP-12265 | SETTLEMENT_LEG_BLOCKED | domain | 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-12266 | VENUE_ROLE_REQUIRED | permission | A role on this venue is required. | Replacing an instrument calendar needs the venue admin role and instrument 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. Granting or revoking the venue admin role also needs a platform admin. | Ask the venue's admin to grant the role to your wallet on this venue's access manager, then repeat the request. To grant or revoke the venue admin role, act as a platform admin. | info | No | 403 |
DALP-12267 | party. | client | 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-12268 | compliance. | dependency | 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 | exec.aa.READ_DEPENDENCY | dependency | 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-12271 | CUSTODY_ | client | The custody provider configuration is not valid here. | The provider or ledger is not enabled on this deployment, the provider lacks a signing capability or does not serve the requested network, the credential fields do not match the provider, the provider identity or exclusivity does not fit the credentials, or no such configuration exists in this organisation. | Choose an enabled provider and ledger that serve the network with the signing capabilities it needs, send the credential fields that provider expects, and name a configuration of your own organisation. | info | No | 422 |
DALP-12272 | CUSTODY_ | domain | 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, recovery needs a successful probe taken after the quarantine, the configuration is not healthy and enabled for new accounts so it cannot serve investors, its stored credential is missing, or a legacy-wallet reconciliation check failed. | Read the configuration, clear what blocks the change, then send the request again. | info | No | 409 |
DALP-12274 | CUSTODY_PROOF_INVALID | client | 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. It also answers when the custody provider refused to sign the operation, for example because signing failed or the wallet cannot pay the fee. | Produce a new proof or confirmation for this account and ledger, then send the request again. | info | No | 422 |
DALP-12275 | CUSTODY_APPROVAL_PENDING | domain | 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-12276 | CUSTODY_ | permission | The custody approval for this request was refused. | The approval this operation waited on was rejected or expired, the wallet's checker refused it, the selected account or provider configuration cannot approve or serve the request, or the session has no active organisation or open invitation. | Start a new request with an account that can approve it, or ask the approver to approve the operation. | info | No | 403 |
DALP-12278 | CUSTODY_ | permission | 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.scope.DENIED | permission | 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-12285 | compliance. | domain | This compliance rule cannot take this change. | The rule's current state does not allow this change here: it may already be on or off, removed, locked, or not supported. | Check the rule's current state where you changed it. If it changed, reload and try again; otherwise this change cannot be made here. | info | No | 409 |
DALP-12286 | compliance. | client | The compliance module settings contradict each other. | Two or more settings in the submitted compliance module configuration cannot hold at the same time. It also answers when a NOT branch excludes holders of a claim topic the system's claim policy manager set to Not allowed. | Submit one consistent module configuration. | info | No | 422 |
DALP-12287 | compliance. | client | The compliance expression is too broad to enforce. | The compliance expression has no positive condition that narrows who it admits, it excludes holders of a claim they can remove themselves without a named acknowledgement, or no topic-scheme registry is indexed to grade that exclusion. | Add a positive condition or narrow the rule. To accept a holder-removable exclusion, send holder as true from a session that is not impersonated. | info | No | 422 |
DALP-12290 | dapi. | dependency | 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-12292 | compliance. | auth | The compliance provider rejected its credentials. | The compliance provider refused the credentials, the credentials are for another provider kind, or the provider does not support the requested topic. | Rotate or correct the provider credentials, then send the request again. | info | No | 400 |
DALP-12293 | compliance. | domain | 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-12295 | core. | client | 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 | core. | client | 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-12297 | core. | operational | 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 | 409 |
DALP-12298 | core. | operational | 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 | 409 |
DALP-12299 | core. | operational | 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 |
The previous page is DALP-12100 to DALP-12199. The next page is DALP-12300 to DALP-12399.