This is the newest version of the TruSTAR API. This version brings some notable improvements upon the previous version (v1.2).
All endpoints that can potentially return large lists of results are paginated, in a standardized way.
Some accept two parameters:
pageNumber (defaults to 0) and
pageSize (defaults to 25, max is 50).
Others require the user to paginate by constantly shrinking the time window for the query by using the
parameters (both will always be in milliseconds since epoch). The reason for not offering a simple
on these endpoints is related to performance.
The JSON response of a paginated endpoint will always have a field called
items, containing the list of results,
and a field called
hasNext, a boolean representing whether a next page exists.
Previous API versions dealt with timestamps in an inconsistent way. In this version, this has been fixed.
If any timestamp, in either a request or a response, is given as an integer, it represents milliseconds since the Unix epoch.
When using request parameters to filter based on time, the filters will always be applied to the resource’s