Skip to content
Chaingateway Docs Chaingateway Docs Chaingateway Docs

Blockchain API FAQ for Developers

This FAQ answers the questions developers ask most often about the Chaingateway API: how to authenticate, which networks exist, how to test, how errors look and how to get support. Chaingateway is a REST API that lets an application create wallets, send transactions, read blockchain data and receive webhooks. Each answer links to the page with the details.

When a request fails: read the ok field and the status in the JSON body, then the message and errors, fix the request, or contact support if the cause is on the server side Send the request Authorization: Bearer YOUR_API_KEY Read ok and status in the JSON body ok: true means the call worked ok: false? Read message and errors 401 token or password, 422 validation or funds Fix the request, or contact support support@chaingateway.io
The error handling loop that the answers below describe.

How do I get started and authenticate?

Section titled “How do I get started and authenticate?”

Register an account, create an API key in the dashboard and send it as a Bearer token. The 7-day free trial needs no card. The Quickstart walks through the first request.

What is Chaingateway.io? Chaingateway.io is a platform providing blockchain API solutions that enable developers to integrate blockchain functionalities into their applications. One REST interface covers wallets, transactions, balances, blocks and webhooks on several blockchain networks.

How do I get started with Chaingateway.io? To get started, sign up for an account on Chaingateway.io. Once registered, you can create an API key in the dashboard under API tokens. You need it to authenticate your API requests. The documentation provides guides and examples to help you integrate the API into your application.

How do I authenticate my API requests? API requests to Chaingateway.io need to be authenticated with an API key. Create the key in the dashboard after logging in. Send it as a Bearer token in the headers of your HTTP requests:

Authorization: Bearer YOUR_API_KEY

A request without a valid token returns HTTP 401 with the body {"message":"Unauthenticated."}. Do not put the key in client-side code or in a repository.

Are there usage limits for the APIs? Yes, there are usage limits based on your subscription plan. Higher-tier plans offer higher usage quotas. Detailed information about the limits and pricing can be found on our pricing page. For example, creating more addresses than your plan allows returns status 422 with the message Your address limit exceeded. Please upgrade your plan.

Which networks and endpoints are available?

Section titled “Which networks and endpoints are available?”

The API supports seven blockchains, each with a mainnet and a testnet, and offers wallet management, transaction handling, webhooks and data retrieval on them. Supported Networks lists the networks and the X-Network header values.

Which blockchain networks are supported? Chaingateway.io supports the following blockchain networks:

  • Ethereum (mainnet and Sepolia)
  • Binance Smart Chain (mainnet and testnet)
  • Bitcoin (mainnet and testnet3)
  • Polygon (mainnet and Amoy)
  • Tron (mainnet and Nile)
  • Arbitrum (mainnet and Arbitrum Sepolia)
  • Solana (mainnet and devnet)

For more information on how to access the different networks, please visit Supported Networks.

What kind of APIs does Chaingateway.io offer? The API covers these areas:

  • Wallet Management: Create and manage wallets.
  • Transaction Handling: Send native coins and tokens, and read transactions.
  • Instant Payment Notification: Receive webhook notifications on blockchain events.
  • Data Retrieval: Fetch blockchain data like balances, blocks and market prices.

The OpenAPI file lists more than 200 operations. The API reference documents each one.

Can I test the APIs in a sandbox environment? Yes, every supported blockchain has a testnet. Add the header X-Network: testnet to a request to run it on the test network. Without the header, or with X-Network: mainnet, the request runs on the main network. This lets you test your integration without moving real funds.

See Supported Networks on how to access the different networks.

How do I handle errors and webhook failures?

Section titled “How do I handle errors and webhook failures?”

Check the ok field of every response, and log message and errors when it is false. Webhook deliveries that fail are not retried automatically. You list them and send them again yourself.

How do I handle errors from the API? If an API request fails, the response includes a status and a message that indicate the issue. The OpenAPI file documents these status codes:

  • 400: Bad Request. Example: the TRC20 contract could not be read.
  • 401: Unauthorized. The API key is invalid or missing, or the wallet password is wrong.
  • 404: Not Found. Example: a webhook id that does not exist.
  • 422: Unprocessable Entity. The request was well-formed, but validation failed or the blockchain rejected the transaction, for example because of insufficient funds.

Check the error handling section in our documentation for more details. We also add useful information within our response body. Here is an example:

{
  "status": 422,
  "ok": false,
  "message": "insufficient funds for gas * price + value: balance 2000000000000, tx cost 195000000000000, overshot 193000000000000",
  "errors": []
}
{
  "status": 422,
  "ok": false,
  "message": "Data validation failed",
  "errors": {
    "password": ["The password field is required."]
  }
}

How do I get notified about incoming payments? Create a webhook with POST /api/v2/{chain}/webhooks. Chaingateway then sends an HTTP POST request to your URL for each matching transaction. Webhooks exist for Ethereum, BNB Smart Chain, Polygon, Arbitrum, TRON and Bitcoin, but not for Solana.

A failed delivery is not retried automatically. List failed notifications with GET /api/v2/{chain}/webhooks/notifications/failed and send one again with POST /api/v2/{chain}/webhooks/notifications/{id}/retry. See Webhooks and Webhooks Security.

Which wallet type should I use? Use a password-protected wallet for long-lived addresses. You send a password when you create the address, and later transactions are signed with that password. Use an unsecured wallet only for temporary addresses, because the private key is returned in the response and you must store it. Chaingateway does not store passwords and cannot restore a lost one. See Wallet Management.

Where can I monitor usage and get support?

Section titled “Where can I monitor usage and get support?”

How can I monitor my API usage? You can monitor your API usage from the dashboard, which provides analytics and reports on the number of requests made, data usage, and any errors encountered.

How do I get support if I encounter issues? For support, you can reach out through our support portal available in the dashboard. We also provide a community forum and extensive documentation that might help resolve common issues.

For urgent matters, contact our support team directly via email at support@chaingateway.io, via Telegram, or via web chat on the website.

We also host a Telegram community where you can find useful discussions.

Is there a referral or partnership program? Yes, we offer referral and partnership programs for developers and businesses interested in promoting Chaingateway.io. For more information, please visit our partnership page.

Where can I find the latest updates and news about Chaingateway.io?

Stay updated with the latest news, feature releases, and announcements by following our blog and subscribing to our newsletter.

Sources

Section titled “Sources”