Errors

Branch on code. rpcCode, reason and hint help debugging and can change.

• bad-request

  HTTP

  400

  Meaning

  Malformed request or data that does not decode, such as bad transaction hex.

  Fix

  Fix the body or the hex.

• unauthorized

  HTTP

  401

  Meaning

  The route needs an API key.

  Fix

  Use a route that needs no key.

• forbidden

  HTTP

  403

  Meaning

  The method is not on the read allowlist.

  Fix

  Sign and send from your wallet or your own node.

• not-found

  HTTP

  404

  Meaning

  No such address history, transaction, block, token or identity.

  Fix

  Check the id. A new address has no history.

• invalid-params

  HTTP

  400

  Meaning

  A parameter has the wrong type or range, or the token does not exist.

  Fix

  Match the route's parameter format and check the token id.

• insufficient-funds

  HTTP

  400

  Meaning

  The balance does not cover the spend.

  Fix

  Fund the address or lower the amount.

• tx-rejected

  HTTP

  422

  Meaning

  The mempool or consensus rejected the transaction. reason carries the node's reject string.

  Fix

  Read reason and hint, then re-sign or raise the fee.

• tx-error

  HTTP

  422

  Meaning

  The transaction spends missing or spent inputs.

  Fix

  Rebuild it from current UTXOs.

• rate-limited

  HTTP

  429

  Meaning

  Too many requests from this IP.

  Fix

  Wait for Retry-After, then retry.

• in-warmup

  HTTP

  503

  Meaning

  The node is starting.

  Fix

  Retry shortly.

• upstream-timeout

  HTTP

  504

  Meaning

  The node did not answer in time.

  Fix

  Retry.

• upstream-unreachable

  HTTP

  502

  Meaning

  The API cannot reach the node.

  Fix

  Retry later.

• internal

  HTTP

  500

  Meaning

  Unclassified error. message carries the node's text.

  Fix

  Retry. Report it if it repeats.