Not Acceptable
When your client only accepts certain formats of data from Frontier and Frontier cannot fulfill that request, Frontier will return a not_acceptable error. This is analogous to the HTTP 406 Error.
If you are encountering this error, please check to make sure the criteria for content you’ll accept is correct.
Attributes
As with all errors Frontier returns, not_acceptable 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 |
Example
$ curl -X GET -H "Accept: application/xml" "https://frontier.testnet.digitalbits.io/accounts/GALWEV6GY73RJ255JC7XUOZ2L7WZ5JJDTKATB2MUK7F3S67DVT2A6R5G"
{
"type": "not_acceptable",
"title": "An acceptable response content-type could not be provided for this request",
"status": 406,
"instance": "node0.frontier.testnet.digitalbits.io/hCYL7oezXs-062662"
}
Related
Edit this doc in GitHub