# Both Error Formats Documented

Gateway errors and application errors have different JSON bodies; the Errors page describes both, with a request and response for each status code.

Source: https://docs.deepinfo.com/changelog/error-formats/

Last updated: 2026-09-26

---
Date: 2026-09-23 · Tags: API, Docs

Errors from the Deepinfo API come in one of these formats, depending on where the request stopped:

- **Gateway errors** cover authentication, plan access, rate limiting and unknown URLs (401, 403, 404,
  429). Their body has `message` and `request_id`.
- **Application errors** cover invalid input, missing resources and unexpected errors (400, 404, 500).
  Their body has `code`, `details`, `parameters` and `solution`.

Error responses also carry a `deepinfo-request-id` header. The `request_id` in a gateway error body is a
different value, so include both when you contact support.

A few errors are not JSON: when a very large export runs too long, the request ends with **502 Bad
Gateway** and a plain-text body. Narrow large exports with filters to avoid it.

[Errors](/getting-started/errors/) lists the messages and codes, with an example request and response for
each one.