Learn how to filter and paginate the Kombo GET
endpoints. This will help you understand how to implement syncs and more.
id
: An ID generated by Kombo, also referred to throughout the documentation as “Kombo ID”.remote_id
: The ID of the object in the remote system. This can be null for some objects.changed_at
: Part of Kombo’s change tracking — this is the timestamp of the last change that was detected by Kombo.remote_deleted_at
: Part of Kombo’s change tracking — this is the timestamp where the object was not found anymore in the remote system.1
. As the integration ID is the same, so will the Kombo ID.next
field or null
. The
value will be a cursor which you can use to get the next page of results. Use
the cursor
query parameter to request the next page. (Please note that you
still need to add the relevant filters while paginating.)
In addition, you can use the page_size
parameter to specify the number of results per page.
updated_after
: Only return objects where the changed_at
value is after
the given timestamp. This can be used to sync data incrementally.
This filter also includes all expanded relations — so if only they have
changed (but none of the primary attributes of the object), this will still
count as the object having changed and it will still be returned.include_deleted
: By default, all values with a remote_deleted_at
value are
not returned. If you want to include them, set this to true
. This is helpful
if you want to remove them from your database.ids
: List of comma-separated ids. Only return objects with these IDs.remote_ids
: List of comma-separated remote ids. Only return objects with
these remote IDs.Header | Sample Value | Description |
---|---|---|
ratelimit-limit | 300 | The maximum number of requests permitted |
ratelimit-remaining | 298 | The remaining number of requests permitted |
ratelimit-reset | 57 | The remaining seconds until the rate limiter is reset |
429
(“Too Many Requests”) status code:
POST
request to fail; you could globally keep track of the ratelimit-remaining
value and keep a certain buffer of requests available to only be used by POST
requests.