1 minute readFixedAgent-ready
Server errors answer JSON with a request id
An unexpected failure on an API route now answers a JSON error with a code, a request id and whether to retry, instead of an HTML error page.
A 500 used to arrive as a web page, so an agent could not read it or tell whether its change had landed. It now carries code: internal_error, a request_id (also in the X-Request-Id header) to quote when you contact us, and retryable: true for a read, false for a write. After a failed write, read the resource back before you retry it.