Troubleshooting · Developer docs

Troubleshooting

Grouped by symptom, never by module, because the person with the problem does not know which module has it. One hundred questions across ten pages, each answered with the causes in the order they usually turn out to be true.

Answer API requests

The selector in my GET body was ignored, and the full record came back

Published

The API reads a GET body only when the request says so, with the header X-Body-Has-Parameters: 1. Without it the body is ignored and the record comes back in its default shape. With it, check three more things:

  • The body is the selector itself, raw and wrapped in braces: {id,name}, not JSON and not properties={id,name}.
  • Only the selector is read from the body. Filters, limit, offset and orderBy in the body are ignored; keep them in the query string.
  • Your HTTP library sends a body on a GET. Some drop it silently: browsers' fetch refuses one, so this is for server-side clients.

See Send a long properties selector in a GET body.

In the API reference: Request bodies.

More in API requests

  1. My filter returned every record
  2. A custom entity list answers a totalCount but no rows
  3. The API answers 404 for a record that exists
  4. My edit saved, but the site did not change
  5. "Invalid reference to related records at activeRevision; expecting an id" when I send activeRevision: true

Was this page helpful?

Your answer goes to the docs team.