Pagination
List endpoints support cursor-based pagination usinglimit and starting_after_id:
has_more field indicating whether additional results exist:
id of the last item as starting_after_id.
If you’re using one of our SDKs, pagination is handled automatically with built-in iterators.
Filtering
Use query parameters to filter results:Filtering by capture time
local_datetime_after and local_datetime_before filter on the asset’s capture time:
- Send offsetless values such as
2024-01-01T00:00:00when you want wall-clock filtering. - Send offset-aware values such as
2024-01-01T00:00:00-05:00when you want an absolute time window. - Keep both bounds consistent. Mixing an offsetless value with an offset-aware value in the same request is rejected.
- Assets with a known capture offset are compared using that offset. Assets without one fall back to wall-clock comparison, so offsetless captures still participate in aware range filters.
local_datetime is serialized, and see the API Reference tab for the full list of available filter parameters for each endpoint.