Skip to main content
Token Management adds a dedicated error range. See the canonical error codes page for all other ranges.

Token error catalog (1700–1749)

CodeTypeHTTPMeaningRetry safe?
1700TOKEN_STANDARD_NOT_SUPPORTED400Unknown or unsupported QRC standard.No
1701TOKEN_TEMPLATE_NOT_FOUND404Unknown template ID.No
1702TOKEN_ALREADY_DEPLOYED409Token already has a confirmed contractAddress.No
1703TOKEN_NOT_DEPLOYED409Operation requires a deployed contract.After deploy completes
1704TOKEN_OPERATION_NOT_ALLOWED422Standard or template does not support the operation.No
1705TOKEN_SUPPLY_EXCEEDED422Resulting supply would exceed supplyPolicy.maxSupply.After reducing amount
1706TOKEN_MINT_NOT_ALLOWED403Caller lacks the on-chain MINTER role.After granting role
1707TOKEN_BURN_NOT_ALLOWED403Caller lacks the on-chain BURNER role.After granting role
1708TOKEN_ROLE_REQUIRED403Caller lacks the on-chain role for the operation.After granting role
1709TOKEN_POLICY_REJECTED422Token-level policy rejected the operation. (See also 1200 POLICY_DENIED.)No
1710TOKEN_APPROVAL_REQUIRED422Approval required and not yet granted. (See also 1201.)After approval
1711TOKEN_CONTRACT_CALL_FAILED502The on-chain contract call reverted.Conditional
1712TOKEN_INVALID_RECIPIENT400Recipient resolution failed.After fixing recipient
1713TOKEN_INVALID_AMOUNT400Amount is zero, negative, or exceeds source balance.After fixing amount
1714TOKEN_COMPLIANCE_RESTRICTION_FAILED422Allowlist, freeze, or compliance check rejected the operation.After fixing eligibility
1715TOKEN_OPERATION_ALREADY_PROCESSED409Operation already reached a terminal state.No
1716TOKEN_DEPLOYMENT_FAILED502Deployment failed during signing or on chain.Conditional

Common patterns

  • All 409 errors indicate state mismatches. Refresh the resource state before retrying.
  • All 422 policy errors require either an approval step, a configuration change, or a different parameter — never raw retries.
  • All 502 errors are transient and may be retried with the same Idempotency-Key.