Not Implemented
If your request method is not supported by Frontier, Frontier will return a not_implemented error. This is analogous to a HTTP 501 Error.
If you are encountering this error, Frontier does not have the functionality you are requesting yet.
Attributes
As with all errors Frontier 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. |
| Instance | String | A token that uniquely identifies this request. Allows server administrators to correlate a client report with server log files. |
Examples
$ curl -X GET "https://frontier.testnet.digitalbits.io/ledgers/200/effects"
{
"type": "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.",
"instance": "node0.frontier.testnet.digitalbits.io/hCYL7oezXs-141917"
}
Related
Edit this doc in GitHub