# Error Handling When you make a request to the CryptAPI API, things can sometimes go wrong. This guide will help you understand the errors you might encounter and how to handle them gracefully. ## Common Issues and Solutions ### Payment Address Not Created **Issue**: Creating a payment address fails with `Please verify your domain before using our service: https://cryptapi.io/verify_domain/` (HTTP 400). With a plugin, the checkout can't create a payment address for the order. **Cause**: the domain of your `callback` URL isn't verified. CryptAPI only creates payment addresses for callback URLs on a verified domain. Our plugins send their callbacks to your store, so for them it's your store's domain. **Solution**: verify the domain once on our [Verify Domain page](https://cryptapi.io/verify_domain), with a DNS TXT record or an HTTPS file. See [How to verify your callback domain](/kb/developers/how-to-verify-your-callback-domain). ### Funds Stuck in Address **Issue**: Funds appear to be stuck in a cryptocurrency address and aren't being processed. **Possible Causes**: - Wrong cryptocurrency sent to the address. Eg. requested funds with `bep20/usdt` ticker and sent `bep20/usdc` - Wrong network (e.g., sending ERC-20 tokens to BSC address) - Minimum transaction amount not met **Solutions**: - Check if the address is valid for the specific cryptocurrency - Verify the minimum transaction amount for the cryptocurrency - If the wrong cryptocurrency was sent to the address and got stuck please [contact our support](https://cryptapi.io/contacts). ### Transaction Not Confirmed **Issue**: Transaction is sent but remains unconfirmed for an extended period. **Possible Causes**: - Network congestion - Transaction stuck in mempool **Solutions**: - Wait for network confirmation (can take 1-24 hours depending on the network) - Check transaction status using the blockchain explorer ### Callback URL Problems **Issue**: Webhook notifications not being received. **Possible Causes**: - Invalid or inaccessible callback URL - Server not responding to webhook requests - Firewall blocking incoming requests - SSL certificate issues **Solutions**: - Ensure callback URL is publicly accessible - Test the URL manually to verify it responds - Check server logs for incoming webhook requests - Verify SSL certificate is valid (for HTTPS URLs) - Make sure your webhook signature verification is working - Add our IPs `51.77.105.132` and `135.125.112.47` to your firewall (or Cloudflare) whitelist By understanding these common errors and issues, you can build more robust integrations and handle problems more effectively. ## Error Response Format When a request fails, CryptAPI answers with JSON: `status` is `error`, and `error` describes the problem. For example, calling [ticker create](/api/tickercreate) without a `callback`: ```json { "status": "error", "error": "You must provide a valid address and a callback" } ``` Check the `status` field as well as the HTTP status code. ## Common Errors These errors can come from more than one endpoint: - `APIs down for maintenance, please check back in a few minutes` (HTTP 503): the whole API is paused for maintenance. Retry in a few minutes. Any endpoint. - `API down for maintenance, please check back in a few minutes` (HTTP 503): the API for this blockchain is paused for maintenance. Retry in a few minutes. Ticker create, logs, info and estimate only. - `ERC20 token "XYZ" is not supported` (HTTP 400): we don't support the token in `{ticker}`. The first word names the network: `BEP20`, `POLYGON`, `TRC20`, `SOL`, `TON` and so on. - `Chain "XYZ" is not supported` (HTTP 400): we don't support the network in `{ticker}`, as in `xyz/usdt`. - `Your request couldn't be processed, please try again later` (HTTP 400): something failed on our side. Retry later. - `Resource not found` (HTTP 404): the URL doesn't exist, for example a ticker we don't support, as in `/xyz/create/`. - `Server error` (HTTP 500): something failed on our side. Retry later, and [contact our support](https://cryptapi.io/contacts) if it keeps happening. Each endpoint also has errors of its own, listed in the **Errors** section of its page: - [Create New Payment Address](/api/tickercreate#errors) - [Check Payment Address Logs](/api/tickerlogs#errors) - [Get Ticker Information](/api/tickerinfo#errors) - [Estimate Blockchain Fees](/api/tickerestimate#errors) - [Payment QR Code Generator](/api/tickerqrcode#errors) - [Convert Prices Using Ticker](/api/tickerconvert#errors) - [Convert Price](/api/convert#errors)