Horizon Error Codes (23 Codes)
Every error returned by Horizon-compatible endpoints on https://pubnet.stellarchain.io conforms to RFC 7807 Problem Details for HTTP APIs and includes a direct "type" link to https://orion.stellarchain.io/horizon-errors/<code>.
bad_request HTTP 400The request you sent was invalid in some way (e.g. malformed query parameter, invalid cursor, invalid asset format, or out-of-range limit).
before_history HTTP 410The requested ledger or cursor predates the earliest ledger retained by this instance.
client_disconnected HTTP 499The client closed the HTTP connection before the server finished sending the response.
forbidden HTTP 403The client is not authorized to access the requested resource.
invalid_accounts_params HTTP 400The `/accounts` collection endpoint requires exactly one filter parameter (`signer`, `sponsor`, `asset`, or `liquidity_pool`).
invalid_order_book HTTP 400The parameters specifying the SDEX order book pair (`/order_book`) are missing or invalid.
method_not_allowed HTTP 405The HTTP method used is not supported for this endpoint.
not_acceptable HTTP 406The client requested a media type in the `Accept` header that the server cannot produce.
not_found HTTP 404The requested URL route, account, ledger, transaction, operation, offer, liquidity pool, or claimable balance does not exist.
not_implemented HTTP 404The requested URL is planned but not yet implemented.
not_supported HTTP 400The requested feature or parameter combination is not supported.
rate_limit_exceeded HTTP 429The client has sent too many requests in a given time window.
resource_limit_exceeded HTTP 422The query exceeded the server's scan/work budget or member fanout limit.
server_error HTTP 500An unexpected internal error occurred while processing the request.
server_over_capacity HTTP 503The server is temporarily overloaded and cannot accept additional concurrent work.
service_unavailable HTTP 503The request cannot be serviced at this time because a required subsystem is warming up or temporarily unreachable.
stale_history HTTP 503The node's ingested history is lagging behind the Stellar network tip beyond the configured staleness threshold.
still_ingesting HTTP 503Data cannot be presented because initial state or order book ingestion is still in progress.
timeout HTTP 504The request or transaction submission timed out before completing.
transaction_failed HTTP 400The transaction was well-formed XDR, but Stellar Core rejected it or one of its operations failed during execution.
transaction_malformed HTTP 400The `tx` parameter could not be decoded as a valid base64-encoded Stellar `TransactionEnvelope` XDR structure.
transaction_submission_timeout HTTP 504The transaction submission timed out waiting for ledger inclusion.
unsupported_media_type HTTP 415The request `Content-Type` header is not supported by this endpoint.
Complete Summary Table
Error Code (type) | HTTP Status | Title | Description |
|---|---|---|---|
bad_request | 400 | Bad Request | The request you sent was invalid in some way (e.g. malformed query parameter, invalid cursor, invalid asset format, or out-of-range limit). |
before_history | 410 | Data Requested Is Before Recorded History | The requested ledger or cursor predates the earliest ledger retained by this instance. |
client_disconnected | 499 | Client Disconnected | The client closed the HTTP connection before the server finished sending the response. |
forbidden | 403 | Forbidden | The client is not authorized to access the requested resource. |
invalid_accounts_params | 400 | Invalid Accounts Parameters | The /accounts collection endpoint requires exactly one filter parameter (signer, sponsor, asset, or liquidity_pool). |
invalid_order_book | 400 | Invalid Order Book Parameters | The parameters specifying the SDEX order book pair (/order_book) are missing or invalid. |
method_not_allowed | 405 | Method Not Allowed | The HTTP method used is not supported for this endpoint. |
not_acceptable | 406 | An acceptable response content-type could not be provided for this request | The client requested a media type in the Accept header that the server cannot produce. |
not_found | 404 | Resource Missing | The requested URL route, account, ledger, transaction, operation, offer, liquidity pool, or claimable balance does not exist. |
not_implemented | 404 | Resource Not Yet Implemented | The requested URL is planned but not yet implemented. |
not_supported | 400 | Not Supported | The requested feature or parameter combination is not supported. |
rate_limit_exceeded | 429 | Rate Limit Exceeded | The client has sent too many requests in a given time window. |
resource_limit_exceeded | 422 | Resource Limit Exceeded | The query exceeded the server's scan/work budget or member fanout limit. |
server_error | 500 | Internal Server Error | An unexpected internal error occurred while processing the request. |
server_over_capacity | 503 | Server Over Capacity | The server is temporarily overloaded and cannot accept additional concurrent work. |
service_unavailable | 503 | Service Unavailable | The request cannot be serviced at this time because a required subsystem is warming up or temporarily unreachable. |
stale_history | 503 | Historical DB Is Too Stale | The node's ingested history is lagging behind the Stellar network tip beyond the configured staleness threshold. |
still_ingesting | 503 | Still Ingesting | Data cannot be presented because initial state or order book ingestion is still in progress. |
timeout | 504 | Timeout | The request or transaction submission timed out before completing. |
transaction_failed | 400 | Transaction Failed | The transaction was well-formed XDR, but Stellar Core rejected it or one of its operations failed during execution. |
transaction_malformed | 400 | Transaction Malformed | The tx parameter could not be decoded as a valid base64-encoded Stellar TransactionEnvelope XDR structure. |
transaction_submission_timeout | 504 | Transaction Submission Timeout | The transaction submission timed out waiting for ledger inclusion. |
unsupported_media_type | 415 | Unsupported Media Type | The request Content-Type header is not supported by this endpoint. |