Skip to main content

​
API Errors

The CDP API v2 uses conventional HTTP response codes to indicate the success or failure of an API request. In general:
  • Codes in the 2xx range indicate success
  • Codes in the 4xx range indicate an error that failed given the information provided (e.g., a required parameter was omitted)
  • Codes in the 5xx range indicate an error on CDP’s backend servers.
    5xx errors are not a guarantee of failure; there’s always the chance that the operation may have succeeded in our back-end. Therefore, your application should treat the operation’s status as unknown.
Each error response includes:
  • errorType: A machine-readable error code
  • errorMessage: A human-readable message providing more detail
  • correlationId: A unique identifier for the request that can help with debugging
  • errorLink: A link to detailed documentation about the specific error type

​
HTTP 400

​
Invalid request

This error occurs when the request is malformed or contains invalid data, including issues with the request body, query parameters, path parameters, or headers. Steps to resolve:
  1. Check all required fields and parameters are present
  2. Ensure request body (if applicable) follows the correct schema
  3. Verify all parameter formats match the API specification:
    • Query parameters
    • Path parameters
    • Request headers
  4. Validate any addresses, IDs, or other formatted strings meet requirements
Common validation issues:
  • Missing required parameters
  • Invalid parameter types or formats
  • Malformed JSON in request body
  • Invalid enum values

​
Transfer-specific validation errors

The following transfer validation scenarios return errorType: "invalid_request". Use the errorMessage field to identify the specific case. Example 1:
Example 2:
Example 3:

​
Unsupported tos language

A submitted Terms of Service acceptance used a language that is not published for the referenced versionId. Steps to resolve:
  1. Read Customer.requirements.tos.tosVersions[] and find the entry whose versionId matches your acceptance.
  2. Choose a language from that entry’s languages list (BCP 47 tags).
  3. Retry with tosAcceptances[].language set to a supported tag.
Example error response:

​
Mandate expired

This error occurs when the mandate is past its expiresAt and can no longer be used. Authorization, approve a mandate, and get wallet approval options return this error. Steps to resolve:
  1. Create a new mandate if the customer should continue
  2. Do not retry the request against the expired mandate
Example 1:
Example 2:

​
Malformed transaction

This error occurs when the transaction data provided is not properly formatted or is invalid. Steps to resolve:
  1. Verify transaction encoding:
    • EVM networks: Check RLP encoding is correct
    • Solana: Validate base64 encoding
  2. Ensure all required transaction fields are present
  3. Validate transaction parameters are within acceptable ranges
  4. Check that the transaction type is supported on the target network
Common causes:
  • Invalid hex encoding for EVM transactions
  • Missing required transaction fields
  • Incorrect parameter formats
  • Unsupported transaction types
  • Network-specific transaction format mismatches
Example error response:

​
Invalid signature

This error occurs when the signature provided for the given user operation is invalid. Steps to resolve:
  1. Verify the signature was generated by the correct owner account
  2. Ensure the signature corresponds to the exact user operation hash
  3. Check that the signature format matches the expected format
  4. Confirm you’re using the correct network for the Smart Account
Common causes:
  • Using wrong owner account to sign
  • Signing modified/incorrect user operation data
  • Malformed signature encoding
  • Network mismatch between signature and broadcast
Example 1:
Example 2:

​
Policy in use

This error occurs when trying to delete a Policy that is currently in use by at least one project or account. Steps to resolve:
  1. Update project or accounts to remove references to the Policy in question.
  2. Retry your delete request.
Example error response:

​
Invalid sql query

This error occurs when the SQL query is invalid or not allowed. Common causes:
  • Using non-SELECT SQL statements (INSERT, UPDATE, DELETE, etc.)
  • Invalid table or column names
  • Syntax errors in SQL query
  • Query exceeds character limit
  • Too many JOIN operations
Example 1:
Example 2:
Example 3:

​
Invalid webhook url

The webhook target URL did not pass scheme, host, address, or endpoint checks. Steps to resolve:
  1. Verify target.url uses HTTPS and responds to HEAD requests with a 200.
  2. Confirm the endpoint is reachable and responds without a server error, then retry.
Example error response:

​
Invalid webhook headers

One or more custom webhook target headers have invalid names or values, duplicate names with different capitalization, or names reserved for delivery metadata and HTTP routing. Steps to resolve:
  1. Check target.headers for invalid names, values, and case-insensitive duplicates.
  2. Remove blocked headers such as Cookie, Host, and X-Webhook-*, then retry.
Example error response:

​
Incompatible event types

The eventTypes in a webhook subscription belong to different scopes that cannot be combined in a single subscription. Steps to resolve:
  1. Group eventTypes by compatible label requirements.
  2. Create a separate webhook subscription for each group.
Example error response:

​
Subscription limit exceeded

The project or entity has reached the maximum number of webhook subscriptions allowed (100). Steps to resolve:
  1. Delete any webhook subscriptions that are no longer needed.
  2. Retry creating the subscription.
Example error response:

​
Unknown

Example 1:
Example 2:

​
Otp verification code invalid

This error occurs when the OTP code submitted to complete a verification is incorrect or has expired (the 10-minute OTP window has elapsed). Steps to resolve:
  1. Ask the user to re-enter the code.
  2. If the OTP window has expired, start a new verification flow.
Example error response:

​
Otp verification invalid

This error occurs when the verification record exists but is not in a usable state for the requested operation. Common causes:
  • The verification is still pending (OTP not yet submitted successfully).
  • The verification has been revoked.
  • The verification channel does not match the expected field (smsVerificationId or emailVerificationId).
Steps to resolve:
  1. Complete a new verification flow and retry.
Example 1:
Example 2:

​
Network not tradable

This error occurs when the selected asset cannot be purchased on the selected network in the user’s location. Steps to resolve:
  1. Verify the asset is tradable on the selected network
  2. Check the user’s location to ensure it is allowed to purchase the asset on the selected network
Common causes:
  • Users in NY are not allowed to purchase USDC on any network other than Ethereum
Example error response:

​
Guest permission denied

This error occurs when the user is not allowed to complete onramp transactions as a guest. Steps to resolve:
  1. Redirect the user to create a Coinbase account to buy and send crypto.
Example error response:

​
Guest region forbidden

This error occurs when guest onramp transactions are not allowed in the user’s region. Steps to resolve:
  1. Redirect the user to create a Coinbase account to buy and send crypto.
Example error response:

​
Phone number verification expired

This error occurs when the user’s phone number verification has expired. Use of guest Onramp requires the user’s phone number to be verified every 60 days. Steps to resolve:
  1. Re-verify the user’s phone number via OTP.
  2. Retry the request with the phoneNumberVerifiedAt field set to new verification timestamp.
Example error response:

​
Otp verification expired

The smsVerificationId or emailVerificationId provided has expired. Verification IDs are valid for 60 days after successful OTP submission. Steps to resolve:
  1. Complete a new verification flow for the user.
  2. Use the new verification ID when creating orders.
Example error response:

​
Otp verification required

An SMS or email verification ID is required on order creation but none was provided. Steps to resolve:
  1. Verify the user’s phone number and email before creating an order.
  2. Pass the returned verification IDs as smsVerificationId and emailVerificationId when creating orders.
Example error response:

​
Otp verification destination mismatch

The phoneNumber or email on the order does not match the destination that was verified. Steps to resolve:
  1. Ensure the phoneNumber or email field on the order matches the destination used during verification.
  2. If the value changed, complete a new verification for the updated phone number or email.
Example error response:

​
HTTP 401

​
Unauthorized

This error occurs when authentication fails. Steps to resolve:
  1. Verify your CDP API credentials:
    • Check that your API key is valid
    • Check that your Wallet Secret is properly configured
  2. Validate JWT token:
    • Not expired
    • Properly signed
    • Contains required claims
  3. Check request headers:
    • Authorization header present
    • X-Wallet-Auth header included when required
Security note: Never share your Wallet Secret or API keys. Example 1:
Example 2:
Example 3:

​
HTTP 402

​
Payment required

This error occurs when an x402 payment is required to access the requested resource. Steps to resolve:
  1. Include a valid x402 payment header in your request
  2. Ensure the payment meets the resource’s pricing requirements
Example error response:

​
Payment method required

This error occurs when a payment method is required to complete the requested operation but none is configured or available. Steps to resolve:
  1. Add a valid payment method to your account using the CDP Portal
  2. Ensure your payment method is valid and not expired
Common causes:
  • No payment method configured on the account
  • Payment method is expired
Example error response:

​
HTTP 403

​
Customer not authorized

This error occurs when the customer is not currently authorized for one or more capabilities required to perform the requested action. This can happen at any point in the customer’s lifecycle and may or may not be resolvable by the developer. The response includes an unauthorizedCapabilities field listing the capability code(s) that were not authorized on this request. Steps to resolve:
  1. Fetch the customer with GET /v2/customers/{customerId} and inspect the requirements field. If requirements.due is non-empty, submit the listed fields via PUT /v2/customers/{customerId} and retry.
  2. If requirements.due is empty, no further action is available — the customer is not currently eligible for this action.
Example 1:
Example 2:
Example 3:

​
Forbidden

This error occurs when you don’t have permission to access the resource. Steps to resolve:
  1. Verify your permissions to access the resource
  2. Ensure that you are the owner of the requested resource
Example 1:
Example 2:
Example 3:

​
Entity not configured for top up

This error occurs when Top-Up is disabled for the entity or required Top-Up configuration is missing or invalid. Steps to resolve:
  1. Contact support or your Coinbase representative to enable Top-Up or correct the entity’s Top-Up configuration
Example error response:

​
Delegation not found

This error occurs when a delegated signing operation is attempted but no active delegation grant exists for the end user (or account). Steps to resolve:
  1. Create a delegation grant using createDelegationForEndUser (user-scoped) or createDelegationForEndUserAccount (account-scoped) before calling the signing or sending operation
  2. If you previously created a grant, it may have expired or been revoked — in those cases you would receive a delegation_expired or delegation_revoked error instead
  3. For account-scoped grants, verify the address in the request matches the granted address (EVM addresses are compared case-insensitively; Solana addresses must match exactly)
Example error response:

​
Delegation expired

This error occurs when the delegation grant used for signing has expired. Delegation grants have a limited lifetime set at creation. Steps to resolve:
  1. Create a new delegation grant using createDelegationForEndUser or createDelegationForEndUserAccount
  2. Retry the signing operation with the new grant active
  3. Consider creating grants with a longer TTL if expiry is frequent
Example error response:

​
Delegation revoked

This error occurs when the delegation grant has been explicitly revoked. Steps to resolve:
  1. Create a new delegation grant using createDelegationForEndUser or createDelegationForEndUserAccount
  2. Confirm with the end user before recreating, since revocation is typically intentional
Example error response:

​
Delegation not authorized

This error occurs when a delegation grant exists but does not authorize the requested operation. Steps to resolve:
  1. For account-scoped grants, verify the signing address matches the address the grant was created for
  2. Check that the operation is permitted for delegated signing on your project
  3. Create a grant with the correct scope if needed
Example error response:

​
Delegation not enabled

This error occurs when delegated signing is attempted on a project that has not enabled the feature. Steps to resolve:
  1. Enable delegated signing in your project configuration via the CDP Portal
  2. Contact support if you believe delegated signing should already be enabled for your project
Example error response:

​
HTTP 404

​
Not found

This error occurs when the resource specified in your request doesn’t exist or you don’t have access to it. Steps to resolve:
  1. Verify the resource ID/address/account exists
  2. Check your permissions to access the resource
  3. Ensure you’re using the correct network/environment
  4. Confirm the resource hasn’t been deleted
Common causes:
  • Mistyped addresses
  • Accessing resources from the wrong CDP project
  • Resource was deleted or hasn’t been created yet
Example 1:
Example 2:
Example 3:

​
Otp verification not found

The provided SMS or email verification ID does not correspond to any verification record. Steps to resolve:
  1. Ensure you are passing the correct verification ID as smsVerificationId or emailVerificationId.
  2. If the issue persists, complete a new verification flow.
Example error response:

​
HTTP 408

​
Timed out

This error occurs when a request exceeds the maximum allowed processing time. Steps to resolve:
  1. Break down large requests into smaller chunks (if applicable)
  2. Implement retry logic with exponential backoff
  3. Use streaming endpoints for large data sets
Example retry implementation:
Example error response:

​
HTTP 409

​
Account not ready

This error occurs when an operation is attempted on an account that is still being provisioned. Steps to resolve:
  1. Wait a few moments and retry the request
  2. If the error persists, the account may still be completing setup — retry with exponential backoff
Example error response:

​
Mandate action pending

This error occurs when an approval or revocation is already in progress for the mandate. Get wallet approval options, approve a mandate, get wallet revocation options, revoke a mandate, and authorize a payment session with a mandate all return this while an action is in flight. Steps to resolve:
  1. Wait for the in-flight approval or revocation to succeed or fail
  2. Check the mandate status, then retry the request
Example 1:
Example 2:

​
Already exists

This error occurs when trying to create a resource that already exists. Steps to resolve:
  1. Check if the resource exists before creation
  2. Use GET endpoints to verify resource state
  3. Use unique identifiers/names for resources
Example 1:
Example 2:
Example 3:

​
HTTP 422

​
Idempotency error

This error occurs when an idempotency key is reused with different parameters. Steps to resolve:
  1. Generate a new UUID v4 for each unique request
  2. Only reuse idempotency keys for exact request duplicates
  3. Track used keys within your application
Example idempotency key implementation:
Example error response:

​
Payment session already authorized

This error occurs when attempting to authorize a payment session that has already been authorized. Steps to resolve:
  1. Check the payment session status — it is already authorized
  2. Proceed to capture, void, or other post-authorization actions as needed
Example error response:

​
Mandate invalid status

This error occurs when the mandate’s status does not satisfy the operation, and a more specific code does not apply. errorMessage names the status the operation expected. Check the specific codes first: mandate_canceled, mandate_revoked, mandate_expired, and mandate_action_pending. Approve a mandate and get wallet approval options require created or approval_failed after those checks. approval_succeeded, revocation_failed, and any other remaining status return this. Authorize a payment session requires approval_succeeded. Revoke a mandate and get wallet revocation options return this when approvedAt was never set, so no spending allowance exists. That is separate from mandate_revoked, which applies only after revokedAt is set. Steps to resolve:
  1. Read errorMessage for the status this operation requires
  2. Move the mandate to that status, or create a new mandate
Example 1:
Example 2:
Example 3:

​
Mandate canceled

This error occurs when canceledAt is set. Authorization, approve a mandate, and get wallet approval options return this. If revokedAt is also set, those operations return mandate_revoked instead. Steps to resolve:
  1. Create a new mandate if the customer should continue
  2. Do not retry the request against the canceled mandate
Example 1:
Example 2:

​
Mandate revoked

This error occurs when the mandate’s on-chain spending allowance has been removed (revokedAt is set, status revocation_succeeded). Authorization, approve a mandate, and get wallet approval options return this when revokedAt is set, including when canceledAt is also set. Get wallet revocation options and revoke a mandate also return this when the allowance was already removed. Cancel a mandate returns this: a fully revoked mandate cannot be canceled. Canceling an already-canceled mandate is a no-op and returns the mandate. Steps to resolve:
  1. Create a new mandate if the customer should continue
  2. Do not retry the request against the revoked mandate
Example 1:
Example 2:
Example 3:

​
Mandate policy violation

This error occurs only when the request breaches the mandate policy: the charge exceeds maxPerAuthorization or maxPerPeriod, or an approval is rejected because the payer’s available balance is below minSetupBalance. Steps to resolve:
  1. Lower the charge, raise the mandate policy, or fund the payer above minSetupBalance
  2. Retry the request
Example error response:

​
Invalid request

This error occurs when the request is malformed or contains invalid data, including issues with the request body, query parameters, path parameters, or headers. Steps to resolve:
  1. Check all required fields and parameters are present
  2. Ensure request body (if applicable) follows the correct schema
  3. Verify all parameter formats match the API specification:
    • Query parameters
    • Path parameters
    • Request headers
  4. Validate any addresses, IDs, or other formatted strings meet requirements
Common validation issues:
  • Missing required parameters
  • Invalid parameter types or formats
  • Malformed JSON in request body
  • Invalid enum values

​
Transfer-specific validation errors

The following transfer validation scenarios return errorType: "invalid_request". Use the errorMessage field to identify the specific case. Example 1:
Example 2:

​
HTTP 429

​
Rate limit exceeded

This error occurs when you’ve exceeded the API rate limits. Steps to resolve:
  1. Implement exponential backoff
  2. Cache responses where possible
  3. Wait for rate limit window to reset
Best practices:
Example 1:
Example 2:
Example 3:

​
Faucet limit exceeded

This error occurs when you’ve exceeded the faucet request limits. Steps to resolve:
  1. Wait for the time window to reset
  2. Use funds more efficiently in your testing
For more information on faucet limits, please visit the EVM Faucet endpoint or the Solana Faucet endpoint. Example error response:

​
Guest transaction limit

This error occurs when the user has reached the weekly guest onramp transaction limit. Steps to resolve:
  1. Inform the user they have reached their weekly limit and will have to wait until next week.
Example error response:

​
Guest transaction count

This error occurs when the user has reached the lifetime guest onramp transaction count limit. Steps to resolve:
  1. Redirect the user to create a Coinbase account to buy and send crypto.
Example error response:

​
HTTP 499

​
Client closed request

This error occurs when the client closes the connection before the server can send a response. Common causes:
  • The client timed out waiting for the server response
  • The client application was terminated during a pending request
  • Network interruption caused the client connection to drop
Steps to resolve:
  1. Increase client-side timeout settings if applicable
  2. Implement retry logic with exponential backoff for long-running queries
  3. Consider optimizing the request to reduce server processing time
Example error response:

​
HTTP 500

​
Internal server error

This indicates an unexpected error that occurred on the CDP servers. Important: If you encounter this error, please note that your operation’s status should be treated as unknown by your application, as it could have been a success within the CDP back-end. Steps to resolve:
  1. Retry your request after a short delay
  2. If persistent, contact CDP support with:
    • Your correlation ID
    • Timestamp of the error
    • Request details
  3. Consider implementing retry logic with an exponential backoff
Note: These errors are automatically logged and monitored by CDP. Example 1:
Example 2:

​
HTTP 502

​
Bad gateway

This error occurs when the CDP API is unable to connect to the backend service. Steps to resolve:
  1. Retry your request after a short delay
  2. If persistent, contact CDP support with:
    • The timestamp of the error
    • Request details
  3. Consider implementing retry logic with an exponential backoff
Note: These errors are automatically logged and monitored by CDP. Example error response:

​
HTTP 503

​
Service unavailable

This error occurs when the CDP API is temporarily unable to handle requests due to maintenance or high load. Steps to resolve:
  1. Retry your request after a short delay
  2. If persistent, contact CDP support with:
    • The timestamp of the error
    • Request details
  3. Consider implementing retry logic with an exponential backoff
Note: These errors are automatically logged and monitored by CDP. Example error response:

​
Endpoint unavailable

This error occurs when a specific endpoint has been temporarily disabled by an operator (e.g. a kill switch). The CDP API as a whole is still healthy; only this endpoint is unavailable. Distinct from service_unavailable, which indicates the API itself is down. Re-enabling is a manual operator action, so the endpoint may remain unavailable for an extended period. Steps to resolve:
  1. Check the CDP status page for an active incident.
  2. If persistent, contact CDP support with:
    • The timestamp of the error
    • Request details
Example error response:

​
HTTP 504

​
Timed out

This error occurs when a request exceeds the maximum allowed processing time. Steps to resolve:
  1. Break down large requests into smaller chunks (if applicable)
  2. Implement retry logic with exponential backoff
  3. Use streaming endpoints for large data sets
Example retry implementation:
Example error response:

​
Network Errors

Network errors occur when there is a problem establishing or maintaining a connection to the CDP API at the network layer. These errors are distinct from API service errors - they indicate that your request never reached the CDP API or was blocked before it could be processed.

​
Understanding Network Errors

When you encounter a network error via the CDP SDK, you’ll receive a NetworkError object with:
  • statusCode: Always 0 (indicating no HTTP response was received)
  • errorType: Specific type of network error
  • errorMessage: Human-readable description
  • networkDetails: Additional information including:
    • code: Technical error code
    • message: Original error message
    • retryable: Whether the operation should be retried

​
Types of Network Errors

​
1. IP Blocked (network_ip_blocked)

Your IP address has been blocked at the gateway level. Common causes:
  • Geographic restrictions.
  • Rate limiting at infrastructure level.
  • Security policies or DDoS protection.
  • Corporate firewall/proxy restrictions.
What to do:
  • Verify you’re not accessing from a restricted region.
  • Check if you’re behind a VPN or proxy that might be blocked.
  • Contact CDP support on Discord if you believe this is in error.
  • This error is not retryable.

​
2. Connection Failed (network_connection_failed)

Unable to establish a connection to the CDP API. Common causes:
  • CDP API is temporarily unavailable. Check the CDP Status Page for any ongoing issues.
  • Network connectivity issues.
  • Firewall blocking outbound HTTPS connections.
  • Incorrect API endpoint configuration.
What to do:
  • Check your internet connection.
  • Verify firewall settings allow HTTPS traffic to api.cdp.coinbase.com.
  • Ensure you’re using the correct API endpoint.
  • This error is retryable. Retry the request with exponential backoff.

​
3. Timeout (network_timeout)

The request took too long and was terminated. Common causes:
  • Network congestion.
  • Slow internet connection.
What to do:
  • Increase timeout settings if consistently timing out.
  • This error is retryable. Retry the request with exponential backoff.

​
4. DNS Failure (network_dns_failure)

Unable to resolve the CDP API domain name. Common causes:
  • DNS configuration issues.
  • Network connectivity problems.
  • DNS server unavailable.
  • Incorrect API endpoint URL.
What to do:
  • Check your DNS settings.
  • Verify network connectivity with nslookup api.cdp.coinbase.com.
  • Try using a different DNS server (e.g., 8.8.8.8).
  • Ensure the API URL is correct.
  • This error is not retryable until DNS is fixed.

​
Handling Network Errors in Code

​
Best Practices

  1. Implement Retry Logic: For retryable errors, use exponential backoff:
  1. Log Network Errors: Always log network errors with full details for debugging.
  2. Monitor Patterns: Track network errors to identify patterns (time of day, specific operations, etc.).
  3. Have Fallback Strategies: Consider implementing fallback mechanisms for critical operations.

​
Troubleshooting Checklist

  • Verify internet connectivity.
  • Check if you’re behind a proxy or VPN.
  • Ensure firewall allows HTTPS traffic to api.cdp.coinbase.com.
  • Verify you’re not in a restricted geographic region.
  • Check DNS resolution: nslookup api.cdp.coinbase.com.
  • Test with curl or similar: curl -I https://api.cdp.coinbase.com/platform.
  • Check if the issue is consistent or intermittent.

​
Getting Help

If you continue to experience network errors after following this guide:
  1. Collect error details including:
    • Full error message and type.
    • Network details from the error.
    • Time and frequency of occurrence.
    • Your network configuration (proxy, VPN, region).
  2. Contact CDP support on Discord with this information.
  3. Check the CDP Status Page for any ongoing issues.
Remember: Network errors are typically environmental issues rather than code problems. Focus on network configuration and connectivity when troubleshooting.