Errors

Every error response uses the same envelope:

{
  "error": {
    "type": "invalid_request",
    "code": "invalid_coord",
    "message": "lat and lng must be finite numbers.",
    "docs_url": "https://wildlife-dev.docs.buildwithfern.com/guides/errors#invalid_coord",
    "request_id": "req_a1b2c3d4e5"
  }
}

Error types

Common error codes

applicable: false is not an error

If a Chora endpoint can’t produce meaningful data for a coord — marine data on an inland property, snow data on a Mediterranean property, MICHELIN in a region we don’t yet cover — the response comes back 200 OK with applicable: false and an empty payload.

Callers should hide the section rather than treat this as an error. It’s how the API tells you “there’s genuinely nothing to show here.”

Partial responses

When one contributing upstream fails during a widget render, the response comes back 200 with meta.partial: true. The successful sections render normally; the failed section is dropped rather than blocking the whole widget.

Request IDs

Every error carries a request_id (also present in successful responses under meta.request_id). Include it in any support request — we can trace the full call path from that alone.