Request

This is what I consider the main endpoint and the main point of contentapi. Through this endpoint, you can request and combine data from the API. You construct requests for data by type, and can construct queries using an SQL-like syntax to constrain your search. You can send parameters as data for part of your search, and can search against previous results in the same request.

For more information, look at the endpoint /api/request/about

What is searchable

All fields you see in the types at /api/request/about are able to be returned in the result, but only the ones marked queryable are usable in either the query or sort options. Some fields are either too expensive to have a query run against them, or just are not suited for such a task because they are complex objects. The sort option still acts like a query, as it compares values against each other to sort, and thus is a form of query and subject to the same restrictions.

There's a lot more on this topic, I just don't have time to do this right now