List events
You can use this endpoint to build a consumer off of your account’s events stream. The event stream is a great fit if you want to process all the changes that have happened to API records. For example, if you’re building workflows or side effects based on change events.
Request parameters
By default, this endpoint returns all events across all syncs and collections in your account. To filter the events returned, you can send along one or all of the following request parameters:
Filter for events for this particular sync.
Defaults to all syncs.
Filter for events from this provider. Value is the provider’s slug, e.g. stripe
. See the list of possible values.
Defaults to all providers.
Filter for events for this collection (e.g. Stripe’s stripe:subscription
or Salesforce’s salesforce:contact
).
Defaults to all collections.
Filter for records with a cursor greater than this value. Used to paginate the stream (see Pagination).
Defaults to null
, which means the first page of records is returned (the earliest records in the stream).
The maximum number of events to return. Can request up to 500 events at a time.
Defaults to 100
.
Response fields
The response is an object that contains an array of event objects:
An array of event objects.
The cursor you can use to fetch the next page of events.
The cursor will always be returned, even if there are currently no more events to fetch. See Pagination below for more details.
The events in the response are ordered by upstream_updated_at
in ascending order (oldest first).
Pagination
The response will always contain a cursor
field, even if there are no more events to fetch. Simply send back the cursor
from the last response to fetch the next page of events.
If you send a cursor
and there are no more events to return, the response will contain an empty events
array and the same cursor
value you sent.
Was this page helpful?