If your request method is not supported by
Horizon, Horizon will return a not_implemented
error. Likewise, if functionality that is intended
but does not exist (thus reserving the endpoint for future use), it will also return a
not_implemented
error. This is analogous to a
HTTP 501 Error.
If you are encountering this error, Horizon does not have the functionality you are requesting.
Attributes
As with all errors Horizon returns, not_implemented
follows the
Problem Details for HTTP APIs
draft specification guide and thus has the following attributes:
Attribute |
Type |
Description |
type |
URL |
The identifier for the error. This is a URL that can be visited in the browser. |
title |
String |
A short title describing the error. |
status |
Number |
An HTTP status code that maps to the error. |
detail |
String |
A more detailed description of the error. |
Example
$ curl -X GET "https://horizon-testnet.stellar.org/offers/1234"
{
"type": "https://stellar.org/horizon-errors/not_implemented",
"title": "Resource Not Yet Implemented",
"status": 404,
"detail": "While the requested URL is expected to eventually point to a valid resource, the work to implement the resource has not yet been completed."
}
Edit this doc in GitHub