# DAPI Error Reference Source: https://docs.settlemint.com/docs/developers/api-integration/dapi-error-reference Complete reference of all DAPI error codes returned by the DALP API, with HTTP status, retryability, and remediation guidance. {/* ENTRY_COUNT:566 */} {/* SURFACE_COUNT:9 */} # DAPI error reference [#dapi-error-reference] DALP returns DAPI error identifiers as stable, machine-readable values in API error responses. Use this page when a DAPI client receives a `DALP-####` code and needs to decide whether to fix the request, refresh indexed state, or retry later. Each error in the registry maps to an HTTP status, retry flag, user-facing reason, and recommended recovery step. SDK clients expose the same fields on `DalpSdkError`: `id`, `category`, `status`, `retryable`, `message`, `why`, `fix`, and optional redacted `details`. 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 resubmitting mutating operations. For non-retryable client, auth, permission, domain, or contract errors, change the request, credentials, permissions, token state, or upstream provider configuration before trying again. If an error tells you to contact support, include the request id from the API response or logs. Do not send secrets, raw signatures, private keys, or unredacted identity documents. Contract revert errors keep their contract-specific data, while DAPI registry metadata explains the API envelope and the safe client response. Compliance-provider errors may require provider-side checks: [Sumsub](https://docs.sumsub.com/), [Elliptic](https://developers.elliptic.co/), [Notabene](https://devx.notabene.id/). ## How to use this reference [#how-to-use-this-reference] 1. Match the `id` in the error envelope to the table row. 2. Check the HTTP status and category to separate request problems from permission, domain, dependency, contract, and operational failures. 3. Use `retryable` as the retry gate. A `yes` means the condition may clear after indexing, dependency recovery, workflow completion, or another transient state change. A `no` means the caller must change something first. 4. Follow the row's fix text. For mutating operations, verify current resource or transaction state before retrying so the client does not submit the same operation twice. ## Errors [#errors] | ID | Category | HTTP status | Retryable | Why | Fix | | ----------- | ----------- | ----------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `DALP-0001` | client | 400 | no | The request is malformed or cannot be understood by the API. | Check the request syntax, parameters, and content type before retrying. | | `DALP-0002` | auth | 401 | no | The request did not include valid authentication credentials. | Authenticate again or send a valid API key/session credential. | | `DALP-0003` | permission | 403 | no | The authenticated actor does not have permission to complete this request. | Use an actor with the required role or ask an administrator to grant access. | | `DALP-0004` | auth | 403 | no | The authenticated user has not completed onboarding required for this operation. | Complete onboarding and retry the request. | | `DALP-0005` | auth | 403 | no | The operation requires wallet-signing protection that is not configured for this user. | Set up PIN or two-factor authentication and retry. | | `DALP-0006` | permission | 403 | no | The actor lacks at least one role required by the token or system contract. | Grant the required role or retry with an authorized actor. | | `DALP-0007` | permission | 403 | no | The encrypted XvP settlement secret could not be decrypted with the caller's current wallet signature. | Retry with the same wallet credentials that were used when the settlement secret was created. | | `DALP-0008` | operational | 500 | no | The API could not determine the effective participant executor for this request after checking the session, organization context, and request headers. | Retry with a valid active organization, X-Participant, and X-Executor header combination. If the problem continues, contact support with the request id. | | `DALP-0009` | auth | 500 | no | The 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. | | `DALP-0010` | dependency | 503 | yes | The API could not build the system context from indexed system registry data. | Retry after the indexer catches up. If the problem continues, contact support with the request id. | | `DALP-0011` | dependency | 503 | yes | The API could not complete a transaction queue operation outside the known contract-error and durable execution engine error mappings. | Retry after a short backoff. If the problem continues, contact support with the request id. | | `DALP-0012` | dependency | 503 | yes | 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. | | `DALP-0013` | dependency | 503 | yes | The API could not preview, sign, or submit the smart-wallet approval workflow after reserving the account-abstraction nonce. | Retry after a short backoff. The nonce reservation is released best-effort and stale reservations expire automatically. | | `DALP-0014` | dependency | 503 | yes | The API could not query the Durable Execution Engine admin plane to determine whether an organization deployment workflow is active. | Retry after a short backoff. If deployment state still cannot be checked, contact support with the request id. | | `DALP-0015` | operational | 503 | yes | The system deployment workflow reached a failed state before producing a usable system address. | Inspect the deployment status and retry after correcting the workflow failure. Include the request id when contacting support. | | `DALP-0016` | operational | 504 | yes | The deployment workflow stayed active but did not publish the system address within the synchronous wait window. | Poll the deployment status or retry with an asynchronous preference instead of waiting for the address in the same request. | | `DALP-0017` | dependency | 503 | yes | The API could not resolve a system factory contract address from the request or directory service before starting deployment. | Retry after the system directory has been configured, or pass an explicit system factory contract address. | | `DALP-0018` | operational | 503 | no | The signer rotation transaction was confirmed, but DAPI could not promote the new signer secret into the secrets provider. | Do not retry blindly. Check the pending signer secret state and rollback status, then recover or rerun the rotation with operator oversight. | | `DALP-0019` | dependency | 503 | yes | An indexer aggregate count could not be converted into a non-negative JavaScript safe integer for the API response. | Retry after the indexer data has been corrected or reindexed. If it continues, contact support with the request id and affected stats endpoint. | | `DALP-0020` | dependency | 503 | yes | The deployment event stream could not read the latest workflow status from the durable execution engine. | Reconnect to the stream or poll deployment status after a short backoff. If it continues, contact support with the request id. | | `DALP-0021` | operational | 503 | no | The deployment workflow ended with a Durable Execution 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. | | `DALP-0022` | client | 404 | no | The requested resource could not be found. | Check the identifier and retry only if the resource should exist. | | `DALP-0023` | client | 409 | no | The request tried to create or register a resource that already exists. | Use the existing resource or choose a unique identifier. | | `DALP-0024` | client | 409 | no | The requested change conflicts with the current resource state. | Refresh the resource state, resolve the conflict, and retry. | | `DALP-0025` | domain | 422 | no | The target token does not expose the interface required for this operation. | Use a compatible token contract or enable the required interface before retrying. | | `DALP-0026` | domain | 403 | no | The DALP system bootstrap has not completed for this environment or organization. | Create or finish deploying the system before calling this operation. | | `DALP-0027` | domain | 501 | no | The requested capability depends on an addon that is not available in this system. | Install or deploy the required addon before retrying the operation. | | `DALP-0028` | domain | 422 | no | The operation targets a token feature that is not attached or enabled. | Enable the required token feature or call an operation supported by this token. | | `DALP-0029` | domain | 403 | no | The authenticated user's email does not match the invitation recipient. | Sign in with the invited email address or ask an admin to send a new invitation. | | `DALP-0030` | domain | 409 | no | The invitation token has already been used successfully. | Continue to the dashboard or ask an admin for a new invitation if access is still missing. | | `DALP-0031` | operational | 504 | yes | 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. | | `DALP-0032` | permission | 403 | no | 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. | | `DALP-0033` | operational | 500 | no | The route or middleware ran without databaseMiddleware even though it needs database access to validate permissions or load resources. | Contact support with the request id; this indicates a server middleware ordering issue. | | `DALP-0034` | permission | 403 | no | 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. | | `DALP-0035` | permission | 403 | no | The request uses a read-only API key on a method that can mutate state. | Use a read-write API key or send the request with a safe read method. | | `DALP-0036` | auth | 403 | no | The request used API key authentication on an endpoint that only accepts session authentication. | Call the REST endpoint with the API key, or authenticate with a supported session for RPC. | | `DALP-0037` | operational | 500 | no | A token-scoped route ran before token middleware attached the indexed token context. | Contact support with the request id; this indicates a server middleware ordering issue. | | `DALP-0038` | operational | 500 | no | The route requires token permissions, but token middleware did not attach user permission state. | Contact support with the request id; this indicates a server middleware ordering issue or missing indexed permission data. | | `DALP-0039` | dependency | 404 | yes | The system exists or is being created, but indexed registry children required by this operation are not available yet. | Retry after the indexer catches up. If the system was never deployed, deploy it first. | | `DALP-0040` | client | 404 | no | The operation requires an indexed system deployment, but none is available for the active organization. | Deploy a system for the organization, wait for indexing, and retry. | | `DALP-0041` | dependency | 500 | yes | The system was indexed without the access-control state required to evaluate the caller's roles. | Retry after indexing catches up. If the problem continues, contact support with the request id. | | `DALP-0042` | dependency | 500 | yes | The route could not load indexed trusted-issuer context for the active system. | Retry after indexing catches up. If the problem continues, contact support with the request id. | | `DALP-0043` | permission | 403 | no | The user's issuer identity is not trusted for the claim topic being mutated. | Use a trusted issuer for the topic, or ask a system manager to trust this issuer for the topic. | | `DALP-0044` | permission | 403 | no | The operation requires a registered issuer identity for the authenticated user. | Register an issuer identity for the user, then retry. | | `DALP-0045` | dependency | 503 | yes | The API could not contact the indexer service that starts blockchain reindex jobs. | Retry after a short backoff. If the problem continues, contact support with the request id. | | `DALP-0046` | client | 400 | no | The requested blockchain reindex range, target, or mode was rejected by the reindex service. | Adjust the reindex request to a supported chain, range, and mode before retrying. | | `DALP-0047` | dependency | 503 | yes | The indexer service accepted the request path but reported that reindexing cannot be started now. | Retry after a short backoff. If the problem continues, contact support with the request id. | | `DALP-0048` | client | 404 | no | No API monitoring log entry exists for the requested id in the active organization. | Verify the log entry id and organization, then retry. | | `DALP-0049` | client | 400 | no | The request type filter does not match a request type known to API monitoring. | Use one of the documented request type values, or omit the filter. | | `DALP-0051` | client | 404 | no | No invitation matching the requested id exists for the caller. | Check the invitation link or ask the organization to issue a new invitation. | | `DALP-0052` | client | 403 | no | The invitation exists but its expiry time has passed. | Ask the organization to send a fresh invitation. | | `DALP-0053` | client | 403 | no | The invitation was explicitly revoked or is no longer in an accepted state for this flow. | Ask the organization to send a fresh invitation. | | `DALP-0054` | client | 404 | no | 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. | | `DALP-0055` | permission | 403 | no | Retrying deployment mutates organization settings and on-chain system state, so member-level access is not sufficient. | Retry with an organization owner or platform administrator account. | | `DALP-0056` | dependency | 503 | yes | The API could not safely inspect or purge the previous durable execution engine workflow before submitting a retry. | Retry after a short backoff. If the problem continues, contact support with the request id. | | `DALP-0057` | permission | 403 | no | The deployment is creating a new organization while the environment restricts organization creation to platform admins. | Ask a platform admin to create the organization or disable the restriction for this environment. | | `DALP-0058` | dependency | 503 | yes | The system directory did not return the factory address required to start deployment. | Retry after directory configuration has propagated. If the problem continues, contact support with the request id. | | `DALP-0059` | client | 404 | no | The settlement exists but the encrypted secret payload is missing from XvP secret storage. | Verify the settlement address and ensure the secret was created before decrypting. | | `DALP-0060` | client | 400 | no | The stored secret payload was encrypted with a method this DAPI version does not support. | Recreate the settlement secret with the supported encryption method. | | `DALP-0061` | client | 400 | no | 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. | | `DALP-0062` | client | 400 | no | The settlement includes an external flow, so a secret or precomputed hashlock is required to coordinate settlement. | Provide a settlement secret or a valid hashlock in the request. | | `DALP-0063` | client | 404 | yes | The requested factory address is not indexed as an XvP settlement addon for the authenticated system. | Use an installed XvP factory address or retry after addon indexing catches up. | | `DALP-0064` | client | 400 | no | The selected XvP factory version requires an ISO 3166-1 numeric country code. | Include a valid country code in the XvP creation request. | | `DALP-0065` | client | 404 | yes | The authenticated system does not have an indexed XvP settlement addon. | Install the XvP settlement addon or retry after indexing catches up. | | `DALP-0066` | client | 404 | no | The request references a system addon address that is not part of the caller's active system. | Use an addon address from the authenticated system. | | `DALP-0067` | client | 400 | no | The XvP list request needs a participant wallet filter and the authenticated user does not have a wallet to use as the default. | Provide a participant wallet filter or complete wallet onboarding. | | `DALP-0068` | client | 404 | yes | The requested settlement address is not indexed for the authenticated system. | Verify the settlement address or retry after indexing catches up. | | `DALP-0069` | permission | 403 | no | The caller is not the local sender recorded for the XvP settlement flow. | Approve from the wallet that is the local sender for this settlement. | | `DALP-0070` | client | 404 | no | 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. | | `DALP-0071` | client | 400 | no | The XvP signature payload is not a 0x-prefixed hexadecimal value. | Sign the settlement message again and submit the hex-encoded signature. | | `DALP-0072` | permission | 403 | no | The authenticated user has no wallet id available for signing the XvP settlement message. | Complete wallet onboarding, refresh the session, and retry. | | `DALP-0073` | dependency | 503 | yes | The wallet signing service failed while signing the XvP settlement message. | Retry after a short backoff. If signing continues to fail, contact support with the request id. | | `DALP-0074` | client | 404 | yes | The requested fixed-yield schedule is not indexed for the authenticated system or addon. | Verify the schedule address or retry after indexing catches up. | | `DALP-0075` | dependency | 503 | yes | The fixed-yield schedule references a denomination asset whose metadata is not available in the indexer. | Retry after indexing catches up. | | `DALP-0076` | dependency | 503 | yes | The fixed-yield operation needs the denomination asset row, but the indexer has not exposed it yet. | Retry after indexing catches up. | | `DALP-0077` | permission | 403 | no | The requested fixed-yield schedule is associated with a different system than the caller's active system. | Use a schedule address from the authenticated system. | | `DALP-0078` | client | 404 | yes | The authenticated system does not have the fixed-yield addon indexed. | Install the addon or retry after indexing catches up. | | `DALP-0079` | dependency | 503 | yes | The fixed-yield deployment transaction completed but the created schedule is not visible in the indexer yet. | Retry after indexing catches up. | | `DALP-0080` | client | 422 | no | The request body or parameters did not match the API contract. | Check the request fields against the API documentation and retry with valid values. | | `DALP-0081` | contract | 422 | no | The smart contract rejected the operation with a known DALP error. | Use the DALP code and suggested response step to correct the request or token state. | | `DALP-0082` | dependency | 503 | yes | A required backend service is temporarily unavailable. | Retry after a short backoff. If the problem continues, contact support with the request id. | | `DALP-0083` | dependency | 503 | yes | The 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. | | `DALP-0084` | unknown | 500 | no | The API could not complete the request because an unexpected server error occurred. | Retry later or contact support with the request id if the problem continues. | | `DALP-0085` | client | 400 | no | The JSON-RPC request is missing required fields or uses an unsupported shape. | Send a valid JSON-RPC 2.0 request with the required method, id, and params fields. | | `DALP-0086` | operational | 500 | yes | The API could not continue the event stream safely. | Reconnect to the stream. If failures continue, contact support with the request id. | | `DALP-0087` | permission | 404 | no | The resource does not exist or is not available to the current actor. | Check that the identifier is correct and that the actor has access to this resource. | | `DALP-0088` | client | 404 | no | DAPI could not find the asset class definition in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0089` | client | 404 | no | DAPI could not find the asset class definition not found definitions delete in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0090` | client | 404 | no | DAPI could not find the asset class definition not found definitions update in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0091` | client | 404 | no | DAPI could not find the asset type template in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0092` | dependency | 503 | yes | The route reached a database query helper that was not registered on the DAPI database context. | Contact support with the request id; this indicates the route is missing the schema or middleware required for this query. | | `DALP-0093` | dependency | 503 | yes | The route reached a database query helper that was not registered on the DAPI database context. | Contact support with the request id; this indicates the route is missing the schema or middleware required for this query. | | `DALP-0094` | dependency | 503 | yes | The route reached a database query helper that was not registered on the DAPI database context. | Contact support with the request id; this indicates the route is missing the schema or middleware required for this query. | | `DALP-0095` | client | 404 | no | DAPI could not find the compliance template in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0096` | client | 404 | no | DAPI could not find the contact in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0097` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0098` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0099` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0100` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0101` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0102` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0103` | client | 404 | no | DAPI could not find the core claim no active found topic identity in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0104` | client | 404 | no | DAPI could not find the core claim no enabled topic scheme found registry in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0105` | client | 404 | no | DAPI could not find the core claims wallet id not found user must issue session includes walletid in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0106` | client | 404 | no | DAPI could not find the core claims wallet id not found user must revoke session includes walletid in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0107` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0108` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0109` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0110` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0111` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0112` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0113` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0114` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0115` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0116` | client | 404 | no | DAPI could not find the exchange rate in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0117` | client | 404 | no | DAPI could not find the exchange rates base currency in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0118` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0119` | client | 404 | no | DAPI could not find the exchange rates no manual rate found in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0120` | client | 404 | no | DAPI could not find the exchange rates quote currency in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0121` | client | 404 | no | DAPI could not find the external token registry in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0122` | client | 404 | no | DAPI could not find the external token registry not found externaltokenregistry deployed registered in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0123` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0124` | client | 404 | no | DAPI could not find the feeds adapters adaptercreated event not found transaction adapter created but address coul in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0125` | client | 404 | no | DAPI could not find the feeds feed address in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0126` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0127` | client | 404 | no | DAPI could not find the feeds get feedsdirectory not found bootstrapped v3 indexer caught up in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0128` | client | 404 | no | DAPI could not find the feeds issuer feedcreated event not found transaction feed created but address could not ex in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0129` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0130` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0131` | client | 404 | no | DAPI could not find the feeds round in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0132` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0133` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0134` | client | 404 | no | DAPI could not find the identity recovery factory address not found user s indicates data integrity issue indexer in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0135` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0136` | client | 404 | no | DAPI could not find the identity recovery no active workflow found user in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0137` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0138` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0139` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0140` | client | 404 | no | DAPI could not find the identity recovery user not found id in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0141` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0142` | dependency | 503 | yes | The route reached a database query helper that was not registered on the DAPI database context. | Contact support with the request id; this indicates the route is missing the schema or middleware required for this query. | | `DALP-0143` | dependency | 503 | yes | The route reached a database query helper that was not registered on the DAPI database context. | Contact support with the request id; this indicates the route is missing the schema or middleware required for this query. | | `DALP-0144` | dependency | 503 | yes | The route reached a database query helper that was not registered on the DAPI database context. | Contact support with the request id; this indicates the route is missing the schema or middleware required for this query. | | `DALP-0145` | dependency | 503 | yes | The route reached a database query helper that was not registered on the DAPI database context. | Contact support with the request id; this indicates the route is missing the schema or middleware required for this query. | | `DALP-0146` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0147` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0148` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0149` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0150` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0151` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0152` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0153` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0154` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0155` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0156` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0157` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0158` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0159` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0160` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0161` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0162` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0163` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0164` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0165` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0166` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0167` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0168` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0169` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0170` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0171` | client | 404 | no | DAPI could not find the settings global organization in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0172` | client | 404 | no | DAPI could not find the settings setting in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0173` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0174` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0175` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0176` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0177` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0178` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0179` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0180` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0181` | client | 404 | no | DAPI could not find the smart wallets approval not found user op hash in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0182` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0183` | client | 400 | no | The smart-wallet approval request included a user operation hash that is not valid hex, so DAPI cannot safely look up or sign the approval. | Send the exact 0x-prefixed userOpHash returned by the smart-wallet preview or approval creation response. | | `DALP-0184` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0185` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0186` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0187` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0188` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0189` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0190` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0191` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0192` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0193` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0194` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0195` | permission | 403 | no | The authenticated wallet is not registered as a signer on the selected multisig validator. | Select a wallet that is a registered signer, or ask a wallet owner to add your signer before retrying. | | `DALP-0196` | permission | 403 | no | The authenticated wallet is not registered as a signer on the selected multisig validator, so it cannot initiate an approval request. | Switch to a registered signer wallet, or ask a wallet owner to add your signer before creating the approval. | | `DALP-0197` | permission | 403 | no | The authenticated wallet is not registered as a signer for the selected smart wallet. | Use a registered signer wallet, or ask a wallet owner to add your signer before retrying. | | `DALP-0198` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0199` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0200` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0201` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0202` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0203` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0204` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0205` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0206` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0207` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0208` | client | 404 | no | DAPI could not find the smart wallets wallet not found address indexed in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0209` | client | 404 | no | DAPI could not find the smart wallets wallet not found address indexed create approval in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0210` | client | 404 | no | DAPI could not find the smart wallets wallet not found address indexed gas status in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0211` | client | 404 | no | DAPI could not find the smart wallets wallet not found address indexed wallets read in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0212` | client | 404 | no | DAPI could not find the smart wallets wallet not found address not indexed yet in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0213` | client | 404 | no | DAPI could not find the smart wallets wallet not found indexing indexer not processed accountcreated event yet in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0214` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0215` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0216` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0217` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0218` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0219` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0220` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0221` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0222` | dependency | 503 | yes | The route ran without middleware context that is required before this branch can execute. | Contact support with the request id; this indicates middleware order or route composition is incorrect. | | `DALP-0223` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0224` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0225` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0226` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0227` | client | 404 | no | DAPI could not find the system addon factory not found indexer in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0228` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0229` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0230` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0231` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0232` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0233` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0234` | client | 404 | no | DAPI could not find the system addon registry in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0235` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0236` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0237` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0238` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0239` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0240` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0241` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0242` | client | 404 | no | DAPI could not find the system claim topic in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0243` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0244` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0245` | client | 404 | no | DAPI could not find the system compliance contract in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0246` | client | 404 | no | DAPI could not find the system compliance module implementations not found indexer in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0247` | client | 404 | no | DAPI could not find the system compliance module not registered registry in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0248` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0249` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0250` | client | 404 | no | DAPI could not find the system factory address not found directory in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0251` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0252` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0253` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0254` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0255` | operational | 500 | no | The route ran without middleware context that is required before this branch can execute. | Contact support with the request id; this indicates middleware order or route composition is incorrect. | | `DALP-0256` | dependency | 503 | yes | The route ran without middleware context that is required before this branch can execute. | Contact support with the request id; this indicates middleware order or route composition is incorrect. | | `DALP-0257` | operational | 500 | no | The route ran without middleware context that is required before this branch can execute. | Contact support with the request id; this indicates middleware order or route composition is incorrect. | | `DALP-0258` | dependency | 503 | yes | The route ran without middleware context that is required before this branch can execute. | Contact support with the request id; this indicates middleware order or route composition is incorrect. | | `DALP-0259` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0260` | client | 404 | no | DAPI could not find the system identity factory address in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0261` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0262` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0263` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0264` | client | 404 | no | DAPI could not find the system identity no contract found wallet in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0265` | client | 404 | no | DAPI could not find the system identity no found in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0266` | client | 404 | no | DAPI could not find the system identity in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0267` | client | 404 | no | DAPI could not find the system identity not found creation indexer did not process block within timeout in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0268` | client | 404 | no | DAPI could not find the system identity not found registry in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0269` | client | 404 | no | DAPI could not find the system identity not registered s registry in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0270` | client | 404 | no | DAPI could not find the system identity not registered yet in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0271` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0272` | client | 404 | no | DAPI could not find the system identity topic not registered scheme registry in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0273` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0274` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0275` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0276` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0277` | client | 404 | no | DAPI could not find the system identity wallet not registered in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0278` | client | 404 | no | DAPI could not find the system no found organization in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0279` | client | 404 | no | DAPI could not find the system in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0280` | dependency | 503 | yes | The route ran without middleware context that is required before this branch can execute. | Contact support with the request id; this indicates middleware order or route composition is incorrect. | | `DALP-0281` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0282` | client | 404 | no | DAPI could not find the system paymaster entrypoint not found indexer not processed directory s in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0283` | client | 404 | no | DAPI could not find the system paymaster not found address indexed list available paymasters via get in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0284` | client | 404 | no | DAPI could not find the requested indexed system paymaster in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0285` | client | 404 | no | DAPI could not find the system paymaster sponsorship not found address in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0286` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0287` | dependency | 503 | yes | The route ran without middleware context that is required before this branch can execute. | Contact support with the request id; this indicates middleware order or route composition is incorrect. | | `DALP-0288` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0289` | client | 404 | no | DAPI could not find the system token factory type in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0290` | client | 404 | no | DAPI could not find the system token no factory found address bootstrapped in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0291` | client | 404 | no | DAPI could not find the system token no factory found contract type not recognized in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0292` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0293` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0294` | client | 404 | no | DAPI could not find the system trusted issuer in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0295` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0296` | client | 404 | no | DAPI could not find the token access control not found manager configured in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0297` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0298` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0299` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0300` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0301` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0302` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0303` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0304` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0305` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0306` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0307` | operational | 500 | no | The route ran without middleware context that is required before this branch can execute. | Contact support with the request id; this indicates middleware order or route composition is incorrect. | | `DALP-0308` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0309` | client | 404 | no | DAPI could not find the token claim topic not registered scheme registry in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0310` | client | 404 | no | DAPI could not find the token compliance no binding found module type contract in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0311` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0312` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0313` | operational | 500 | no | The route ran without middleware context that is required before this branch can execute. | Contact support with the request id; this indicates middleware order or route composition is incorrect. | | `DALP-0314` | client | 404 | no | DAPI could not find the token create factory type in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0315` | operational | 500 | no | The durable token-creation workflow reported a failed phase before producing a result; `data.phase` and `data.error` carry the on-chain or workflow-side failure reason. | Inspect `data.error` for the underlying revert or workflow message. Retry only if the cause is transient; otherwise surface the workflow error to the user. | | `DALP-0316` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0317` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0318` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0319` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0320` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0321` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0322` | client | 404 | no | DAPI could not find the token documents document group not found replacement in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0323` | client | 404 | no | DAPI could not find the token documents document in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0324` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0325` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0326` | client | 404 | no | DAPI could not find the token documents file not found storage upload failed in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0327` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0328` | client | 404 | no | DAPI could not find the token factory in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0329` | operational | 500 | no | The route ran without middleware context that is required before this branch can execute. | Contact support with the request id; this indicates middleware order or route composition is incorrect. | | `DALP-0330` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0331` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0332` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0333` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0334` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0335` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0336` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0337` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0338` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0339` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0340` | client | 404 | no | DAPI could not find the token indexer token in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0341` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0342` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0343` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0344` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0345` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0346` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0347` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0348` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0349` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0350` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0351` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0352` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0353` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0354` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0355` | client | 404 | no | DAPI could not find the token sale addon in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0356` | client | 404 | no | DAPI could not find the token sale addon not found addons in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0357` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0358` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0359` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0360` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0361` | client | 404 | no | DAPI could not find the token sale no registered identity found must create in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0362` | client | 404 | no | DAPI could not find the token sale not found indexer in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0363` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0364` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0365` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0366` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0367` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0368` | client | 404 | no | DAPI could not find the token transfer fromwallet not registered identity registry wallet must onboarded can in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0369` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0370` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0371` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0372` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0373` | permission | 403 | no | The authenticated actor does not satisfy the ownership, signer, role, or organization permission required by this branch. | Retry with an authorized actor, select the correct organization or wallet, or ask an administrator to grant the required permission. | | `DALP-0374` | client | 404 | no | DAPI could not find the token transfer not found address deployed indexed in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0375` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0376` | client | 404 | no | DAPI could not find the token transfer towallet not registered identity registry wallet must onboarded can in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0377` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0378` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0379` | client | 404 | no | DAPI could not find the token transfer wallet not registered identity registry must onboarded approving transfers in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0380` | client | 404 | no | DAPI could not find the token transfer wallet not registered identity registry must onboarded revoking approvals in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0381` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0382` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0383` | client | 404 | no | DAPI could not find the transaction in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0384` | client | 404 | no | DAPI could not find the transaction not found not chain no stored queue record hash in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0385` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0386` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0387` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0388` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0389` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0390` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0391` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0392` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0393` | client | 404 | no | DAPI could not find the user kyc document in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0394` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0395` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0396` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0397` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0398` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0399` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0400` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0401` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0402` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0403` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0404` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0405` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0406` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0407` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0408` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0409` | client | 404 | no | DAPI could not find the user kyc file not found storage upload failed in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0410` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0411` | client | 404 | no | DAPI could not find the user kyc no data found profile but version history not completed verification yet in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0412` | client | 404 | no | DAPI could not find the user kyc no profile found delete already removed in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0413` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0414` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0415` | domain | 409 | no | The request conflicts with the current resource, workflow, or domain state for this branch. | Refresh the resource state, make the required state transition first, or choose an operation that is valid for the current state. | | `DALP-0416` | client | 404 | no | DAPI could not find the user kyc profile in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0417` | client | 404 | no | DAPI could not find the user KYC profile for this request in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0418` | client | 404 | no | DAPI could not find the user kyc source version not found initialdata new users in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0419` | client | 404 | no | DAPI could not find the user kyc version in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0420` | client | 404 | no | DAPI could not find the user KYC version for this request in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0421` | client | 404 | no | DAPI could not find the user kyc version not found version read in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0422` | operational | 500 | no | DAPI reached a branch-specific operational failure while executing this route. | Retry if the operation is idempotent. If it continues, contact support with the request id and route name. | | `DALP-0423` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Adjust the request fields to satisfy this endpoint requirement, then retry. | | `DALP-0424` | client | 404 | no | DAPI could not find the user in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0425` | client | 404 | no | DAPI could not find the user not found by wallet in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0426` | client | 404 | no | DAPI could not find the user not found get security in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0427` | client | 404 | no | DAPI could not find the user not found national id in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0428` | client | 404 | no | DAPI could not find the user not found password reset in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0429` | client | 404 | no | DAPI could not find the user not found reset mfa in the active system, organization, or indexer scope. | Verify the identifier, ownership scope, and indexing state before retrying. | | `DALP-0430` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0431` | dependency | 503 | yes | A required downstream dependency, indexed record, workflow, storage service, or chain provider was not available for this branch. | Retry after the dependency or indexer catches up. If it continues, contact support with the request id. | | `DALP-0432` | dependency | 503 | yes | The indexer has not linked the fixed-yield schedule to its token metadata yet. | Retry after indexing catches up. | | `DALP-0433` | domain | 409 | no | The capital-raise-limit compliance module stores configuration that cannot be changed after the module instance has been installed. | Deploy a new capital-raise-limit module instance with the required parameters, then update token compliance to use that instance. | | `DALP-0434` | client | 400 | no | The token uses the legacy compliance model, which has no scoped module bindings and cannot atomically update module parameters with a scope. | Use configureComplianceModule for legacy tokens, or migrate the asset to a current compliance-engine token before configuring scoped modules. | | `DALP-0435` | client | 400 | no | The token uses the legacy compliance model, which supports only the single-instance compliance-module install flow. | Use installComplianceModule for legacy tokens, or migrate the asset to a current compliance-engine token before installing scoped module instances. | | `DALP-0436` | client | 400 | no | The token uses the legacy compliance model, which has no per-instance scope state to update. | Use legacy compliance-module configuration routes for legacy tokens, or migrate the asset to a current compliance-engine token before setting module scope. | | `DALP-0437` | dependency | 400 | no | A durable execution engine endpoint returned HTTP 400 before DAPI could complete the downstream operation. | Retry only after verifying the API request shape and workflow input. If the request is valid, contact support with the request id. | | `DALP-0438` | dependency | 401 | no | A durable execution engine endpoint returned HTTP 401, so DAPI could not authenticate the downstream workflow call. | Retry after the service credentials are corrected. If you are an API consumer, contact support with the request id. | | `DALP-0439` | dependency | 403 | no | A durable execution engine endpoint returned HTTP 403, so the downstream workflow refused DAPI's call. | Retry after the workflow permissions or service identity are corrected. If you are an API consumer, contact support with the request id. | | `DALP-0440` | dependency | 404 | yes | A durable execution engine endpoint returned HTTP 404, which means the expected workflow service, handler, or invocation target was not available. | Retry after the workflow deployment and service discovery have caught up. If it continues, contact support with the request id. | | `DALP-0441` | dependency | 409 | no | A durable execution 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. | | `DALP-0442` | dependency | 422 | no | A durable execution engine endpoint returned HTTP 422 because the downstream workflow accepted the call envelope but rejected its semantic input. | Verify the requested operation is valid for the current resource state. If the request is valid, contact support with the request id. | | `DALP-0443` | dependency | 500 | no | A durable execution engine endpoint returned HTTP 500 while processing the downstream operation. | Retry if the operation is idempotent. If it continues, contact support with the request id so the workflow failure can be investigated. | | `DALP-0444` | dependency | 504 | yes | A durable execution engine endpoint returned HTTP 504 before the downstream operation completed. | Check the resource or deployment status before retrying so you do not duplicate a workflow step that may still complete. | | `DALP-0445` | dependency | 400 | no | The transaction queue returned BAD\_REQUEST before a transaction could be accepted for processing. | Verify the route input, wallet verification payload, and queued transaction parameters before retrying. | | `DALP-0446` | dependency | 409 | no | The transaction queue returned CONFLICT because the requested transaction cannot be accepted in the current queue or resource state. | Refresh the transaction or resource state, wait for any active queued operation to finish, then retry if the operation is still valid. | | `DALP-0447` | dependency | 422 | no | The transaction queue accepted the operation envelope but rejected its semantic transaction input before dispatch. | Verify the requested chain operation is valid for the current contract and token state before retrying. | | `DALP-0448` | dependency | 504 | yes | 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. | | `DALP-0449` | client | 404 | no | The migration comparison route needs the active system address before it can compare deployed component implementations. | Set the SYSTEM\_ADDRESS setting or deploy a system, then retry the comparison. | | `DALP-0450` | client | 400 | no | The migration comparison route needs the directory contract address from the active network configuration. | Set networks.\.contracts.directory in config.yml for the default network, then retry the comparison. | | `DALP-0451` | dependency | 404 | yes | The directory contract address is configured, but the indexer has not produced the directory row needed for component comparison. | Retry after the indexer processes the directory registration. If it continues, contact support with the request id. | | `DALP-0452` | client | 400 | no | The migration start route needs an active organization before it can resolve the system and workflow scope. | Select an organization, then start the migration again. | | `DALP-0453` | client | 404 | no | The migration start route needs the active system address before it can submit the migration workflow. | Deploy a system or set the SYSTEM\_ADDRESS setting, then start the migration again. | | `DALP-0454` | auth | 403 | no | The migration start route needs the authenticated account wallet before it can verify migration permissions. | Connect a wallet to your account, then start the migration again. | | `DALP-0455` | auth | 403 | no | The authenticated wallet does not hold a role that is allowed to start the system migration workflow. | Use an account with the system manager or admin role, or ask an admin to grant the role before retrying. | | `DALP-0456` | client | 400 | no | The migration start route needs the directory contract address from the active network configuration. | Set networks.\.contracts.directory in config.yml for the default network, then start the migration again. | | `DALP-0457` | domain | 409 | yes | The migration workflow journal still has an active invocation for this organization. | Wait for the current migration to finish, then retry if another migration is still needed. | | `DALP-0458` | dependency | 500 | yes | DAPI could not reset the previous system migration workflow journal and state before submitting a fresh run. | Retry in a moment. If the problem continues, contact support with the request id. | | `DALP-0459` | client | 400 | no | The migration workflow needs a connected sender wallet and wallet id for the on-chain transactions. | Connect a wallet, then start the migration again. | | `DALP-0460` | dependency | 500 | no | The system migration workflow reported a terminal failure: {reason} | Review the failed migration step and retry after correcting the underlying issue. If it continues, contact support with the request id. | | `DALP-0461` | domain | 409 | yes | Another add/remove claim-topic mutation for this trusted issuer is already running. DAPI does not queue same-key callers behind the database lock because that can consume database pool sessions. | Wait for the active mutation to finish, then retry the claim-topic request if the issuer's topic set still needs to change. | | `DALP-0462` | domain | 422 | no | 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. | | `DALP-0463` | client | 409 | no | The organization already has a non-system template with the submitted name. | Choose a unique template name or update the existing template instead. | | `DALP-0464` | client | 404 | no | DAPI could not find an account with native-balance state in the active system scope. | Verify the chain ID, address, system selection, and indexer freshness before retrying. | | `DALP-0465` | client | 400 | no | The configured maturity-redemption treasury is a smart contract. ERC-20 `approve` must be called from the contract that owns the funds, which this route cannot do on its behalf. | Call `approve(spender, amount)` directly from the treasury contract (e.g. via its admin or governance flow), or reconfigure the feature to use an externally-owned treasury wallet. | | `DALP-0466` | client | 404 | yes | The maturity-redemption feature row for this token has not been created or the indexer has not processed the feature initialization yet, so denomination asset and treasury are still unset. | Verify the token has the maturity-redemption feature attached and wait for the indexer to catch up, then retry. | | `DALP-0467` | client | 403 | no | 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. | | `DALP-0468` | dependency | 503 | yes | The indexer populates `treasury_is_contract` via a single `eth_getCode` on every `MaturityRedemptionFeatureCreated` / `TreasuryUpdated`, but the column is still `null` for this feature — the indexer has not finished the classification step yet (typical during a partial reindex / backfill). Without that flag we cannot decide whether the approve flow is allowed (EOA treasuries) or must be blocked (contract treasuries), so we refuse to proceed rather than risk a misclassified on-chain failure. | Wait for the indexer to catch up and retry. If the column stays `null` for an extended period, verify the indexer is healthy and that `MaturityRedemptionFeatureCreated` / `TreasuryUpdated` for this feature were ingested. | | `DALP-0469` | client | 400 | no | The native-balance history endpoint limits each page to 100 rows to keep indexer queries bounded. | Request 100 or fewer history rows per page and use the pagination links for additional rows. | | `DALP-0470` | client | 400 | no | The native-balance history endpoint requires a lower block bound so history scans stay within the supported query window. | Include `filter[since]` with a block number using the `gte` or `eq` operator, then retry. | | `DALP-0471` | client | 404 | no | DAPI 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. | | `DALP-0472` | auth | 403 | no | 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. | | `DALP-0473` | dependency | 503 | yes | The indexer populates `treasury_is_contract` via a single `eth_getCode` on every `FixedTreasuryYieldFeatureCreated` / `TreasuryUpdated`, but the column is still `null` for this feature — the indexer has not finished the classification step yet (typical during a partial reindex / backfill). Without that flag we cannot decide whether the approve-yield-allowance flow is allowed (EOA treasuries) or must be blocked (contract treasuries), so we refuse to proceed rather than risk a misclassified on-chain failure. | Wait for the indexer to catch up and retry. If the column stays `null` for an extended period, verify the indexer is healthy and that `FixedTreasuryYieldFeatureCreated` / `TreasuryUpdated` for this feature were ingested. | | `DALP-0474` | client | 409 | no | Compliance modules that price mint amounts in fiat (currently capital-raise-limit) require an IDALPPriceResolver addon registered on the system. The dapi resolves the addon address server-side and injects it into the module's initialization payload — without an installed addon there is no resolver to inject, so the deployment is refused before any on-chain transaction is queued. | Install the PriceResolver addon on this system (Addons → Price Resolver) before creating tokens whose compliance template includes capital-raise-limit, adding capital-raise-limit to an existing token, or updating its parameters. | | `DALP-0475` | domain | 409 | no | The platform-wide Account Abstraction feature flag is disabled, so smart wallets cannot be selected as default wallets for routed transactions. | Enable the platform Account Abstraction feature flag, or create the smart wallet without setting it as default. | | `DALP-0476` | domain | 409 | no | The platform-wide Account Abstraction feature flag is disabled, so smart wallets cannot be selected as default wallets for routed transactions. | Enable the platform Account Abstraction feature flag, or update only the smart wallet metadata. | | `DALP-0477` | domain | 409 | no | `conversion-minter` declares `dependsOn: ["conversion"]` in the addon registry. Publishing a template with the minter but no conversion would produce a runtime-invalid token (a minter with nothing to mint into). | Add the missing dependency to `requiredFeatures` (or remove the orphan dependent), then retry the publish or update request. | | `DALP-0478` | dependency | 422 | yes | Before `redeem(amount)` runs, the dapi handler reads `allowance(treasury, featureAddress)` on the denomination asset and compares it to the on-chain `calculatePayout(amount)` payout. The treasury is an externally-owned wallet and its ERC-20 allowance to the maturity-redemption feature contract is below that payout, so `TreasuryPayoutLib.payoutFrom` would revert with `ERC20InsufficientAllowance` inside the redeem transaction. The preflight refuses up front so the redeemer is not charged gas for a doomed tx. | Sign in as the configured treasury wallet (see `data.treasury`) and grant the maturity-redemption feature an allowance of at least `data.required` base units of the denomination asset via the bond's Manage maturity → Approve allowance control, then retry the redemption. Since ERC-20 `approve` overwrites (not adds), agents should submit `data.required` as the approve amount, not `data.required - data.allowance`. The error's `data` payload carries `allowance` and `required` as base-unit decimal strings, plus the `denominationAsset`, `feature`, and `treasury` addresses. | | `DALP-0479` | client | 422 | yes | The maturity-redemption feature's `isMatured` flag is still `false` and the on-chain `maturityDate` has not been reached, so `_MaturityRedemptionFeatureLogic.redeem` would revert with `BondNotYetMatured`. The preflight refuses up front so the redeemer is not charged gas for a doomed tx. | Wait until the configured `maturityDate` is reached and the bond is matured, or call `mature(token)` / `matureEarly(token, actualMaturityDate)` if you hold the maturity role and want to settle early. Retry once the feature is matured. | | `DALP-0488` | auth | 401 | no | 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. | | `DALP-0489` | client | 400 | no | 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. | | `DALP-0490` | domain | 404 | no | A compliance webhook referenced an external subject ID that has not been mapped to a DALP identity or wallet. | Create the subject through DALP before accepting provider webhooks for that external ID, or reconcile the event from the audit log. | | `DALP-0491` | domain | 404 | no | The webhook target is not currently available for compliance event intake. | Verify the provider configuration and resume the provider before sending more provider events. | | `DALP-0492` | domain | 409 | no | The compliance provider failed provisioning or health checks and cannot process provider events. | Repair or reprovision the provider before retrying webhook processing. | | `DALP-0493` | domain | 422 | no | 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. | | `DALP-0494` | domain | 409 | no | The event timestamp or sequence is behind the last applied event for the same provider, subject, and topic. | Do not replay stale provider events; inspect the audit event if the provider's ordering guarantees appear broken. | | `DALP-0495` | dependency | 503 | yes | DAPI could not reach the provider health endpoint or the provider returned an unhealthy response. | Retry after a short backoff; if the failure persists, verify provider availability and provider credentials. | | `DALP-0496` | dependency | 502 | no | 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. | | `DALP-0497` | contract | 502 | no | The tenant trusted issuer registry rejected the provider issuer EOA registration transaction. | Verify the provider issuer address, claim topic, tenant registry address, and transaction trace before retrying provisioning. | | `DALP-0498` | domain | 400 | no | The webhook payload declared a claim topic that is not configured on the provider. | Add the topic to the provider, or correct the provider adapter topic mapping. | | `DALP-0499` | domain | 404 | no | A wallet-subject compliance provider event referenced a wallet that DALP could not resolve to an OnchainID identity. | Register the wallet to an OnchainID identity before creating or replaying the compliance subject mapping. | | `DALP-0500` | domain | 410 | no | 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. | | `DALP-0501` | client | 409 | no | 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. | | `DALP-0502` | client | 404 | no | DAPI could not find the compliance provider in the active organisation scope. | Verify the provider identifier and ownership scope before retrying. | | `DALP-0503` | client | 404 | no | DAPI could not find the requested topic on the compliance provider. | Verify the webhook identifier and provider before retrying, or add a new topic through the provider webhook add endpoint. | | `DALP-0504` | client | 400 | no | The selected vendor product cannot attest the requested claim topic. | Choose one of the provider's supported topics or select a different provider kind. | | `DALP-0505` | client | 409 | no | Single-topic provider products have exactly one webhook; revoking it would leave the participant with no supported topics. | Revoke the compliance provider instead, or add another supported webhook before revoking this one. | | `DALP-0506` | contract | 502 | no | The on-chain identity factory rejected the claim-issuer participant identity deployment for the compliance provider. | Verify the system identity factory and signer configuration, then retry provisioning. The provider row stays in failed status until provisioning succeeds. | | `DALP-0507` | client | 429 | yes | The tenant has exhausted the replay-specific webhook rate-limit bucket. | Wait for the Retry-After interval before starting another replay. | | `DALP-0508` | client | 400 | no | The replay request spans more blocks or events than the API allows in a single replay job. | Split the replay into smaller ranges and retry. | | `DALP-0509` | domain | 409 | no | 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. | | `DALP-0510` | auth | 401 | no | 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. | | `DALP-0511` | permission | 404 | no | 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. | | `DALP-0512` | client | 400 | no | 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. | | `DALP-0513` | domain | 409 | no | 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. | | `DALP-0514` | client | 409 | no | The same Idempotency-Key was previously used for a request with a different method, path, or body hash. | Reuse an Idempotency-Key only for the same request, or send a new key for a different request. | | `DALP-0515` | client | 409 | yes | Another request with the same Idempotency-Key is still being processed for this tenant. | Wait for the in-flight request to finish, then retry the same request. | | `DALP-0516` | client | 409 | no | The endpoint URL change cannot proceed silently — there are pending delivery attempts the dispatcher would re-target to the new URL. | Re-send the request with `?acknowledgePending=true` to confirm those deliveries should target the new URL, or wait for the queue to drain. | | `DALP-0517` | client | 422 | no | Switching an endpoint to `defaultPayloadShape='fat'` requires an explicit GDPR ceremony — the operator must acknowledge each `<eventType>.<fieldPath>` that the thin shape would have stripped. The ack on the request didn't cover every PII field for the endpoint's subscriptions, so the switch would have silently broadened the consent surface. | Resend the PATCH with `fatEventsAcknowledgment.fieldsAcknowledged` set to the full list of `<eventType>.<fieldPath>` paths returned by `getWebhookFatAcknowledgmentFields(subscriptions)` — the dapp's switch-to-fat dialog computes this automatically. | | `DALP-0518` | dependency | 503 | yes | The API could not contact the Durable Execution Engine admin endpoint required to inspect or mutate workflow state. | Retry after a short backoff. If the problem continues, check the Durable Execution Engine cluster health and contact support with the request id. | | `DALP-0519` | client | 404 | no | The Durable Execution Engine admin API does not currently report a deployment matching the configured service URL. | Confirm the durable service is registered with Durable Execution Engine (force-redeploy if needed) and retry. | | `DALP-0520` | client | 409 | no | The workflow has an active invocation, has already succeeded, or its prior invocations could not be purged. | Inspect the workflow with the doctor route and resolve the blocking invocation before retrying. | | `DALP-0521` | dependency | 408 | yes | The Thales Luna 7 partition was waiting on out-of-band m-of-n approval and the configured retry window elapsed before the operator quorum signed off, so the workflow gave up. | Activate the partition on the HSM and re-submit the transaction. If expiries are frequent, lengthen the signing window via the signer config (luna.quorum.retryWindowMs). | | `DALP-0522` | dependency | 409 | no | The Luna vendor-extension reported the partition as activated, but the signing call still returned m-of-n-pending three times in a row. Either the firmware misreports activation or a concurrent caller is consuming the quorum. | Inspect the partition state on the HSM directly. If activation is genuinely pending, retry once the operator approves; otherwise contact support with the request id so the classification heuristic can be tuned. | | `DALP-0523` | domain | 422 | no | The token's transaction-fee rates have been permanently frozen on-chain. The mutation was rejected before reaching the queue. | Frozen rates cannot be modified. Update the fee recipient instead, or deploy a new token if different rates are needed. | | `DALP-0524` | permission | 404 | no | The requested participant cannot be selected by the authenticated session. | Remove the X-Participant header or retry with the authenticated participant id. | | `DALP-0525` | dependency | 502 | no | 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. | | `DALP-0526` | client | 404 | no | DAPI could not find the webhook endpoint in the authenticated tenant scope. | Verify the endpoint identifier and tenant context before retrying. | | `DALP-0527` | client | 404 | no | DAPI could not find the webhook delivery in the authenticated tenant scope. | Verify the delivery identifier, endpoint identifier, and tenant context before retrying. | | `DALP-0528` | client | 404 | no | DAPI could not find the webhook replay in the authenticated tenant scope. | Verify the replay identifier, endpoint identifier, and tenant context before retrying. | | `DALP-0529` | client | 404 | no | DAPI could not find the webhook receipt in the authenticated tenant scope. | Verify the receipt identifier, delivery identifier, and tenant context before retrying. | | `DALP-0530` | client | 400 | no | The X-Executor header requested EOA execution for a participant type that cannot execute from an EOA. | Use X-Executor: smart-wallet or omit the header so the API selects the participant's supported executor. | | `DALP-0531` | client | 404 | yes | The X-Executor header requested smart-wallet execution, but no smart wallet is available for this participant and organization. | Wait for smart-wallet provisioning or indexing to complete, then retry. | | `DALP-0532` | domain | 409 | no | Mutually-exclusive token features bind to the same on-chain or accounting path and would either double-account the same transfer or contradict each other. The registry models these pairs so the publish path can reject them before a token is created from the template. | Remove one feature from each conflicting pair in `requiredFeatures`, then retry the publish or update request. | | `DALP-0533` | client | 404 | no | DAPI 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. | | `DALP-0600` | domain | 409 | no | Removing a target currency would orphan its on-chain feed. Feeds can only be added. | Submit a value that is a strict superset of the existing target currencies. | | `DALP-0601` | client | 422 | no | The provider's supported-currency snapshot does not contain every requested code. | Pick currencies from the supported-currencies endpoint, or wait for the next provider refresh if you expect the code to appear. | | `DALP-0602` | dependency | 503 | yes | The addCurrencyFeeds workflow dispatch was not durably accepted. The new currencies were not persisted. | Retry the request. If it continues, contact support with the request id. | | `DALP-0603` | permission | 403 | no | Adding a target currency requires the caller's wallet to hold FEEDS\_MANAGER\_ROLE on the system AccessManager so the workflow's IssuerSignedScalarFeedFactory.createFeed call does not revert; the indexed access-control state shows the wallet is not a current member of that role. | Have a system manager grant FEEDS\_MANAGER\_ROLE to this wallet on the system, then retry. The setting is not persisted until the dispatch succeeds. | | `DALP-0604` | domain | 422 | no | The active chain has no FeedsDirectory wired up (V3-style deployment), so the workflow's IssuerSignedScalarFeedFactory.createFeed path that backs TARGET\_CURRENCIES additions cannot execute. Persisting the addition would leave the setting reflecting a currency with no path to a feed. | Use a system deployed on a chain that supports FeedsDirectory, or remove the new currency from the requested TARGET\_CURRENCIES value. | | `DALP-0605` | domain | 422 | no | Both features bind to the token transfer path and would account for the same transaction fee twice. | Remove one of the conflicting features from the template's `requiredFeatures` or `featureConfigs`. | | `DALP-0606` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | Wait for the next yield period to complete or check the conversion history. | | `DALP-0607` | client | 400 | no | The request reached a branch whose input failed route-specific validation before the operation could be executed. | The closure was set at the time of conversion. Past-closure yield is no longer claimable. | | `DALP-0608` | client | 400 | no | 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. | | `DALP-0609` | dependency | 503 | yes | DAPI could not verify or decrypt the stored KYC document envelope. | Retry later. If the document remains unavailable, contact support with the request id. | | `DALP-0610` | client | 400 | no | The uploaded KYC document payload was not valid base64 document data. | Read the document bytes, base64-encode them without data URL prefixes, and retry. | | `DALP-0611` | client | 400 | no | The declared KYC document size did not match the bytes decoded from fileData. | Send the raw file byte length in fileSize and retry the upload. | | `DALP-0612` | client | 400 | no | The KYC document MIME type did not match the file signature detected by DAPI. | Upload a JPEG, PNG, WebP, or PDF whose file extension and MIME type match the actual bytes. | | `DALP-0613` | dependency | 503 | yes | DAPI could not resolve an organization Vault EOA that can sign price-feed submissions for the organization identity. | Retry after organization deployment and indexing complete. If it continues, contact support with the request id. | | `DALP-0614` | permission | 400 | no | The requested platform setting change requires permissions to be synced before it can be persisted. | Ask an administrator to run Sync permissions for the listed participants, then retry. | | `DALP-0615` | client | 400 | no | 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. | | `DALP-0616` | client | 403 | no | 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. | | `DALP-0617` | domain | 403 | no | 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. | | `DALP-0618` | client | 404 | no | Every `directory.*` v2 route resolves the on-chain global Trusted Issuers Registry or Topic Scheme Registry via the per-network Directory address and the indexed `directoryInstances` table. The route returns 404 when either the Directory address is missing for the active chain or the indexed Directory has no `GLOBAL_TRUSTED_ISSUERS_REGISTRY` / `GLOBAL_TOPIC_SCHEME_REGISTRY` instance row. | Confirm the platform's Directory address is configured for the active chain and that the global registry instances have been indexed before retrying. | | `DALP-0619` | client | 404 | no | The `directory.topicSchemes.*` route looked up a topic scheme on the resolved global Topic Scheme Registry but no row matched the supplied name. The indexer reflects the on-chain registry, so a missing row means the scheme has not been registered on the global tier (or has been removed) for the active chain. | Confirm the topic scheme name (case-sensitive, no normalization) and that the indexer has caught up with the latest on-chain register/remove events before retrying. | | `DALP-0620` | client | 409 | no | Upserting a directory topic scheme is idempotent on `(name, signature)` — submitting the exact same pair returns the existing row. When the name is already registered with a different signature, the registry would silently rewrite the on-chain claim shape and break every system that inherits the scheme, so the route refuses the request before touching the chain. | Delete the existing scheme (only safe if no child registry has surfaced a stale-signature warning) or pick a new name. To change the signature in-place, call the dedicated update path once the indexed signature has been confirmed compatible. | | `DALP-0621` | client | 403 | no | 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. | | `DALP-0622` | client | 404 | no | Per-token topic-scheme writes target the token's own Topic Scheme Registry, resolved from the indexed `identityRegistries.topicSchemeRegistryAddress` column. The route returns 404 when that column is null or no `identityRegistries` row exists for the token — the token inherits schemes only through the system → global chain and has nowhere to register a token-specific scheme. | Attach a token-level Topic Scheme Registry to the token before adding or removing token-specific schemes. Token-level schemes cannot be managed until the registry exists; inherited system and global schemes remain visible on the list in the meantime. | | `DALP-0623` | client | 404 | no | Removing a per-token topic scheme resolves the URL `topicId` to an indexed row on the token's own Topic Scheme Registry. The route returns 404 when the topic id matches no token-level row — it resolves to an inherited system or global scheme, to nothing in the resolved chain, or to a token-level scheme the indexer has not caught up to yet. Inherited schemes are not removable through this route. | Confirm the topic id belongs to a token-level scheme (inheritanceLevel `token`) on the resolved chain. If the scheme was just added, wait for the indexer to catch up with the on-chain register event before retrying the delete. | | `DALP-0624` | client | 404 | no | Per-token trusted-issuer writes target the token's own Trusted Issuer Registry, resolved from the indexed `identityRegistries.trustedIssuersRegistryAddress` column. The route returns 404 when that column is null or no `identityRegistries` row exists for the token — the token inherits issuers only through the system → global chain and has nowhere to register a token-specific issuer. | Attach a token-level Trusted Issuer Registry to the token before adding or removing token-specific issuers. Token-level issuers cannot be managed until the registry exists; inherited system and global issuers remain visible on the list in the meantime. | | `DALP-0625` | client | 404 | no | Removing a per-token trusted issuer resolves the URL `issuerAddress` to an indexed row on the token's own Trusted Issuer Registry. The route returns 404 when the issuer address matches no token-level row — it resolves to an inherited system or global issuer, to nothing in the resolved chain, to an issuer in another token's registry, or to a token-level issuer the indexer has not caught up to yet. Inherited issuers are not removable through this route. | Confirm the issuer address belongs to a token-level issuer (inheritanceLevel `token`) on the resolved chain. If the issuer was just added, wait for the indexer to catch up with the on-chain add event before retrying the delete. | | `DALP-0626` | permission | 403 | no | The generic feeds submit route is not role-gated for price administration; price-topic submissions must flow through token set-price so the token-level admin role check applies. | Call POST /v2/tokens/{tokenAddress}/price with a caller holding the token setPrice role. | | `DALP-0632` | client | 404 | no | The detach or rotate route resolves the live instance by typeId on the token; no `isAttached = true` row exists for that typeId. | Verify the typeId in the URL and that the feature was previously attached. Re-fetch the token's feature list and retry against an attached typeId. | | `DALP-0634` | client | 404 | no | Reading or replacing a token's compliance expression resolves the token's own identity registry from the indexed `identityRegistries` row. The route returns 404 when no `identityRegistries` row exists for the token — the token has no identity registry indexed, so it has no compliance expression to read or to write. | Confirm the token has a deployed identity registry and that the indexer has caught up with its deployment. The compliance expression cannot be read or replaced until the identity registry is indexed. | | `DALP-0635` | operational | 503 | no | The chain is missing a gas-pause profile, 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. | | `DALP-0636` | permission | 403 | no | The requested platform setting change needs to bind existing OnchainIDs to smart wallets, and the caller does not hold every required identity-sync role on the effective executor. | Retry as an account that holds DEFAULT\_ADMIN\_ROLE and IDENTITY\_MANAGER\_ROLE on the active system. | | `DALP-0637` | domain | 409 | no | 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. | | `DALP-0638` | domain | 409 | no | 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. | | `DALP-0639` | client | 422 | no | The on-chain IssuerSignedScalarFeed.submit() guard ObservedAtTooFarInFuture() reverts the transaction when observedAt exceeds block.timestamp by more than the feed's driftAllowance. Accepting the request would queue a transaction that will revert and wedge the workflow. | Clamp the producer's observedAt to the latest block.timestamp for the target chain, or check the signer host's wall clock against NTP if values are minutes ahead. | | `DALP-0640` | client | 422 | no | The `/v2/tokens/{tokenAddress}/treasury/health` route resolved a feature row whose `treasury` column is the zero address. The badge cannot compose a meaningful balance, allowance, or status against the zero address, so the route refuses up front rather than surface a misleading `red` badge. | Use the bond or yield feature's Set treasury control to configure a non-zero treasury wallet, then refetch the treasury-health endpoint. | | `DALP-0641` | dependency | 502 | yes | The treasury-health badge issues exactly one live `IERC20.balanceOf(treasury)` call against the configured chain provider. That call either reverted or could not be reached, so the badge cannot render an authoritative balance and refuses to fall back to indexer state (the balance is operator-mutable and the indexer's `tokenBalances` row would be stale). | Retry once the chain provider is reachable. If the failure persists, verify the configured RPC endpoint for the active chain and the denomination asset address before retrying. | | `DALP-0642` | client | 422 | no | The `/v2/tokens/{tokenAddress}/treasury/health` route composes one badge against a single treasury wallet, denomination asset, and implementation classification. When the maturity-redemption and fixed-treasury-yield features attached to the same token resolve to different values for any of those, a single-treasury badge would compare one feature's allowance against another feature's balance and report a misleading status, so the route fails closed instead. | Reconfigure the maturity-redemption and fixed-treasury-yield features so they share the same treasury wallet, denomination asset, and implementation classification, then refetch the treasury-health endpoint. | | `DALP-0643` | dependency | 503 | yes | The `/v2/tokens/{tokenAddress}/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. | | `DALP-0644` | client | 404 | yes | 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. | | `DALP-0645` | client | 400 | no | 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. | | `DALP-0646` | client | 400 | no | 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. | | `DALP-0647` | client | 400 | no | 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. | ## Surface coverage [#surface-coverage] | Surface | Transport | Coverage | Public adapter behavior | | -------------------------------------------- | --------- | ----------- | ------------------------------------------------------------------------------------------------------------ | | Better Auth | hono | excluded | pass-through | | Known contract revert | orpc-rest | proof-slice | Preserve CONTRACT\_ERROR data and DALP code while adding unified registry metadata. | | Durable execution engine dependency failures | orpc-rest | proof-slice | Return retryable dependency guidance through the unified public envelope. | | Indexer database dependency failures | orpc-rest | in-scope | Report degraded indexer schema reads through registry observability while preserving safe fallback behavior. | | Bundler JSON-RPC handler | json-rpc | proof-slice | Preserve JSON-RPC 2.0 error framing and include registry data under error.data. | | oRPC RPC | orpc-rpc | proof-slice | Carry the same registry identity and public copy through the RPC-compatible error payload. | | oRPC REST | orpc-rest | proof-slice | Return the unified public error envelope for current REST failures. | | DAPI SSE streams | sse | proof-slice | Emit a protocol-valid error event after stream start or direct envelope before stream start. | | Hono unknown fallback | hono | proof-slice | Return the safe unknown public envelope after redaction and telemetry emission. |