Errors
Every error that Frysis itself generates, on api.frysis.com and on your proxy host, is an RFC 9457 problem with Content-Type: application/problem+json:
{ "type": "https://docs.frysis.com/errors/invalid_token", "title": "Invalid payload token", "status": 422, "detail": "Not a valid payload token", "instance": "/v1/payloads/fry1.abc", "code": "invalid_token"}| Field | Meaning |
|---|---|
type |
A URL identifying the kind of error; it opens that error’s page in the error reference. |
title |
Short summary, the same for every occurrence of this type. |
status |
The HTTP status code. |
detail |
What went wrong in this request. |
instance |
The request path. |
code |
Machine-readable code. Switch on this in your code. |
errors |
Present when there are several problems: [{ "detail": "…" }]. |
request_id |
Proxy calls only; matches the frysis-request-id header. |
Responses that an upstream returns through a proxy call are passed through unchanged and don’t use this format.
Retrying
Section titled “Retrying”Retry 429, 503 and 504 with backoff, honouring Retry-After when present. Don’t retry other 4xx errors without changing the request.