Skip to main content
This page is the resolution target of the RFC 9457 type URI on every invalid_expand problem body: https://docs.get-exo.com/errors/invalid_expand. HTTP status: 422 Unprocessable Content.

Why it happens

Responses are lean by default and grow only when you ask. Each route publishes its own set of expandable relations, and an unknown name fails loudly rather than being ignored. POST /v1/retrieve supports one relation: sources.content, which replaces the 280-character snippet with the full stored text.

How to fix it

  • Read the valid values out of detail and suggestedAction. Both list exactly what the route supports.
  • Omit expand to get the lean response.