Who this is for. Anyone choosing field names for a selector, a filter or a payload, and anyone tempted to write their own API document for a project.

Declared in code, generated from it

Each entity has an API response model in the platform's code. It lists the properties and relations a response can carry, which are exactly the names properties selects and the names a filter can use (where they are stored fields). The documentation of that model is generated from the code, so it is right for the version of the platform it was generated from, and it changes when the code does.

A hand-maintained API document, including one your own team writes for a project, will be wrong within a month as the model changes. Link to the generated pages instead of copying them.

Where to find it

You needGo toMade
The fields and relations of a record in a responseThe model in the Reference, for example Blogs › Blog, “API & Jobs” viewGenerated from the code
A module's routesThe module under RoutesGenerated from the code
Every endpoint, with parameters, requests in five languages and real responsesThe API referenceWritten from the platform team's Postman collection, the route tables and live requests to this site
How to use it all, with worked examplesThis guideWritten by hand

The model view answers “what can I select?”. The API reference answers “what do I send, and what comes back?”. Most questions need both: the reference for the request, the model for the field names.

Which to trust first

Trust them in this order:

  1. A real response from your site. Ask for the field and look. A name that does not exist comes back as an Error: Getter for property … not found string, so the question is settled in one request.
  2. The generated model. It is read from the code.
  3. The API reference. Its examples are real, but they were captured on a given day and on this site's data.
  4. This guide. It explains behaviour, and is checked against the platform, but it does not list every field.

If you find a difference, the feedback strip at the foot of every page reaches the people who maintain them.