This page lists the 100 errors the Platform API can return with a code from DALP-0000 to DALP-0499. 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-0001 | BAD_REQUEST | client | The request could not be read. | A check on this route refused the request as invalid, and no more specific error code covers that check. | Check the field names, types, and content type against the route schema, then send the request again. | info | No | 400 |
DALP-0002 | UNAUTHORIZED | auth | 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-0003 | FORBIDDEN | permission | 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-0004 | NOT_ONBOARDED | auth | 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 | USER_MISSING_2FA | auth | 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-0006 | USER_NOT_AUTHORIZED | permission | 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-0009 | SESSION_ | dependency | 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_ | dependency | 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_ | dependency | 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-0021 | DEPLOYMENT_ | operational | 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-0022 | NOT_FOUND | client | 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 | client | 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 | CONFLICT | client | 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-0025 | TOKEN_ | domain | 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 | domain | 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-0031 | CONFIRMATION_TIMEOUT | operational | 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-0032 | ADMIN_ACCESS_REQUIRED | permission | 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_ | permission | 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-0036 | SESSION_POLICY_DENIED | auth | 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-0045 | REINDEX_ | dependency | Ledger Data reindex admin is unreachable. | The platform could not contact the Ledger Data 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-0046 | REINDEX_REQUEST_INVALID | client | Reindex request wasn't accepted. | The Ledger Data reindex admin rejected the range, target or mode of this reindex request, or the network catalogue has no single enabled entry for the requested chain. | Adjust the reindex request to a supported chain, range, and mode before retrying. | info | No | 400 |
DALP-0048 | API_ | client | 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 | client | 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_INVALID | client | 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_NOT_FOUND | client | 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-0076 | FIXED_ | dependency | 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-0080 | INPUT_VALIDATION_FAILED | client | 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-0082 | SERVICE_UNAVAILABLE | dependency | 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 | n/a | dependency | 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-0084 | INTERNAL_SERVER_ERROR | unknown | The platform could not complete this request. | An unexpected failure occurred after the request passed validation. | Read the state the request would change before you send it again. If the failure continues, contact support with the X-Request-Id response header. | error | No | 500 |
DALP-0091 | ASSET_ | client | Asset type template not found. | No asset type template with this id is visible to your organisation, or the template is a draft or hidden from issuance. | 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-0115 | TOKEN_ | dependency | 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-0116 | EXCHANGE_RATE_NOT_FOUND | client | Exchange rate not found. | No active FX feed covers the requested currency pair on the current chain, or the feed exists but has not 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 | FEEDS_ | client | 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 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 | FEEDS_ | client | FeedsDirectory not found for this system. | The platform found no FeedsDirectory address for this system in the index, or the request resolved no system. The system has not completed its V3 bootstrap, or the indexer has not 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-0131 | FEED_ROUND_NOT_FOUND | domain | 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-0147 | OFFCHAIN_ | permission | Your organisation role does not grant the permission this operation needs. | Your role in the active organisation does not grant the off-chain permission this route requires. | Ask an organisation owner for a role that grants the permission, then retry. | info | No | 403 |
DALP-0148 | OFFCHAIN_ | permission | 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-0151 | DURABLE_ | dependency | The workflow engine call failed. | The workflow execution service could not reach its message store, had no runner free to accept the call, or was already handling this exact request. | Retry the request. If the problem persists, contact support with the request ID. | error | Yes | 503 |
DALP-0175 | SETTINGS_ | client | 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. | Keep the theme within its limits: at most 32 KiB for the whole payload, exactly the required token set in light and dark, at most 500 KiB per embedded logo and at most 5 MiB for an uploaded logo file. Then send it again. | info | No | 400 |
DALP-0227 | SYSTEM_ | client | Addon factory {factoryAddress} was not found in the indexer. | Coupon operations run on the token's fixed-treasury-yield feature, and none is attached to this token. | Attach the fixed-treasury-yield feature to the token, then send the request again. | info | No | 404 |
DALP-0242 | SYSTEM_ | client | 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 | SYSTEM_ | client | The compliance module is not registered. | The active system has no compliance module registry, the registry holds no entry for this module, the chain's directory has no implementation of the requested module type, or the token has no indexed identity registry. | 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 | SYSTEM_ | client | 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-0262 | SYSTEM_ | operational | 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-0272 | SYSTEM_ | client | 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 | client | 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 | SYSTEM_ | client | Paymaster {paymasterAddress} not found. | 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 /api/v2/system/paymasters to list all paymasters currently indexed for this system. | info | No | 404 |
DALP-0284 | SYSTEM_ | client | Paymaster {systemAddress} not found. | 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 be indexed yet. | Confirm the paymaster address is correct and that the indexer has processed the registration transaction. Use GET /api/v2/system/paymasters to list all paymasters currently indexed for this system. | info | No | 404 |
DALP-0285 | SYSTEM_ | client | Sponsorship paymaster not found with address {paymasterAddress}. | The address is not this organisation's active indexed paymaster on this network. | Use the paymaster address that GET /api/v2/system/paymasters returns for this network. | info | No | 404 |
DALP-0294 | SYSTEM_ | client | 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 /api/v2/system/trusted-issuers to list registered issuers. | info | No | 404 |
DALP-0314 | TOKEN_ | client | 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-0315 | TOKEN_ | domain | 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-0316 | TOKEN_ | client | Token creation needs a templateId. | DALP asset creation requires an instrument template identifier. | Select an instrument template and retry the request. | info | No | 422 |
DALP-0318 | TOKEN_ | domain | 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-0321 | TOKEN_ | client | Declared file size does not match actual file size in storage. | The stored object's byte length differs from the fileSize in the confirm-upload request. The platform removed the object 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. | info | No | 422 |
DALP-0322 | TOKEN_ | client | Document group not found for replacement. | The replaceGroupId supplied in the request does not name a document group of the requested documentType on this token. A new version keeps the type of the group it replaces, so a group whose latest live document has another type is not found either. | List the token's current documents and resubmit with the groupId of a document of the same documentType, or omit replaceGroupId to start a new group. | info | No | 404 |
DALP-0323 | TOKEN_ | client | Document not found. | The document ID matches no non-deleted document for this token. The document was deleted, or the ID belongs 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 | TOKEN_ | client | 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-0325 | TOKEN_ | operational | 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-0326 | TOKEN_ | client | File not found in storage. | No file exists at the expected storage location, so the pre-signed upload did not finish before the confirm step. | 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 | TOKEN_ | client | Object key is outside the permitted path for this token. | The objectKey in the request does not start with the expected token- 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_ | client | 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-0330 | TOKEN_ | dependency | Fixed-treasury-yield feature state is not indexed for this token yet. | The index has no fixed-treasury-yield record (denomination asset and treasury address) for this token, or the record holds zero-address values. The index has not processed the feature initialisation event yet. | 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-0332 | TOKEN_ | client | No yield is claimable until the first yield period completes. | 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-0333 | TOKEN_ | dependency | 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 | TOKEN_ | dependency | Indexed data validation failed. | A field in the indexed token or feature inventory does not match the expected format. | Do not retry the request. It fails the same way until the indexed data is repaired. Report the X-Request-Id response header to the platform operator. | error | No | 500 |
DALP-0340 | TOKEN_ | client | Token {address} has no historical-balances feature. | Historical balance reads use the token's historical-balances feature, and none is attached to this token. | Attach the historical-balances feature to the token, then read again. | info | No | 404 |
DALP-0343 | TOKEN_ | domain | Token price cannot be resolved from the indexed pricing state. | data.reason names the failed price state: no-feed has no registered feed; feed-not-indexed has no indexed row; registration- 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-0345 | TOKEN_ | auth | An on-chain identity is required to set a token price. | The authenticated participant has no on-chain identity on the request chain, or the organisation has no eligible CLAIM signer to sign price declarations. | Create or select a participant identity on the request chain, then retry the token price update. If the message names the CLAIM signer, set up the organisation's claim signer first. | info | No | 403 |
DALP-0346 | TOKEN_ | domain | The price feed system is not installed. | The active system has no issuer-signed price-feed factory. | Install the price feed system before setting token prices. | error | No | 503 |
DALP-0347 | TOKEN_ | client | 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-0351 | LEGACY_BOND_NOT_INDEXED | operational | The bond is not indexed yet for this token. | 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-0353 | TOKEN_ | permission | Delegated redemption requires the custodian role. | Redeeming for owner {owner} requires the custodian role. | Redeem from the caller's own wallet, or ask a token custodian to redeem for another owner. | info | No | 403 |
DALP-0357 | TOKEN_ | permission | 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-0372 | TOKEN_ | client | Missing transfer item. | The transfers array is empty. A transfer request needs at least one item. | Provide at least one transfer item in the transfers array and retry. | info | No | 422 |
DALP-0375 | TOKEN_TRANSFER_PAUSED | domain | Token {tokenAddress} is halted. | Token operations are halted, so transfers are disabled. | Resume token operations before transferring. | info | No | 409 |
DALP-0383 | TRANSACTION_NOT_FOUND | client | Transaction {requestId} 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-0388 | USER_ | domain | 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 with POST /api/, then retry the approval once the version reaches under_review status. | info | No | 409 |
DALP-0389 | USER_ | domain | Cannot fulfill request with status “ {value}”. Fulfillment requires an open request. | The KYC action request is not open: it was fulfilled or cancelled, or no such request exists. | Verify the current status of the action request before retrying. Only open action requests can be fulfilled. | info | No | 409 |
DALP-0390 | USER_ | domain | 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 | USER_ | domain | 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 | USER_ | domain | 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-0417 | USER_ | client | 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-0431 | XVP_ | dependency | The completed settlement write is not indexed yet. | The settlement or token-sale write completed on chain, but its result was not readable from the index before the read window closed. | Do not send the write under a new Idempotency-Key, because it already completed. Repeat the request unchanged with the same Idempotency-Key to read its result once it is indexed. Contact support with the X-Request-Id response header if it keeps failing. | error | Yes | 503 |
DALP-0441 | DURABLE_ | dependency | 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_ | dependency | 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_ | dependency | 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-0462 | SETTINGS_ | domain | 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-0463 | SETTINGS_ | client | A template with this name already exists in this organisation. | The organisation already has a custom template with the submitted name. | Choose a unique template name or update the existing template instead. | info | No | 409 |
DALP-0467 | TREASURY_WALLET_MISMATCH | client | Caller wallet is not the treasury wallet for the fixed-treasury-yield 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 | SYSTEM_ | client | 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-0472 | STEP_UP_REQUIRED | auth | 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-0474 | PRICE_ | domain | 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-0488 | COMPLIANCE_ | auth | Webhook authentication failed. | The compliance webhook signature could not be verified against the provider's signing secret. | Verify the provider webhook URL and signing secret configuration, then send a freshly signed event. | info | No | 401 |
DALP-0489 | COMPLIANCE_ | client | Webhook timestamp is outside the accepted replay window. | The compliance webhook event carries no timestamp, or its timestamp is more than five minutes from the server clock. | Send a fresh provider event with a current timestamp and verify clock synchronization for the provider. | info | No | 400 |
DALP-0491 | COMPLIANCE_ | domain | Compliance provider is not accepting webhook events. | The compliance provider is paused, so its webhook accepts no events. | Verify the provider configuration and resume the provider before sending more provider events. | info | No | 404 |
DALP-0492 | COMPLIANCE_ | domain | 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_ | domain | Compliance provider event has no supported mapping. | The provider payload is not JSON, or does not match a supported ClaimSource verdict or monitoring-alert shape. A parsed payload is kept for audit when the audit write succeeds. | Review the provider event type and update the adapter mapping before replaying the event. | info | No | 422 |
DALP-0496 | COMPLIANCE_ | dependency | 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 |
The next page is DALP-0500 to DALP-0599.