ApiProblemDetails
Error body returned by the API. It follows RFC 7807 application/problem+json: type, title, status, detail and instance carry the standard fields, and code adds a stable machine-readable identifier of the specific error condition. Match on code rather than on title or detail, which are meant for humans and may be reworded.
URI reference identifying the problem type, as defined by RFC 7807. Branch on code instead.
Short human-readable summary of the problem type. Written for humans and may be reworded, so do not match on it.
HTTP status code of the response, repeated in the body.
Human-readable explanation of what went wrong in this specific case.
URI reference identifying this specific occurrence of the problem.
Stable machine-readable discriminator for the specific error condition. Omitted from the body when absent.
Error body returned by the API. It follows RFC 7807 application/problem+json: type, title, status, detail and instance carry the standard fields, and code adds a stable machine-readable identifier of the specific error condition. Match on code rather than on title or detail, which are meant for humans and may be reworded.
{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"code": "string"
}