Skip to main content
Every list endpoint returns one page at a time, newest first. Two lists are also feeds: the revocations list and the events list can be read oldest first from a point you choose, so you can process each item once.

The list envelope

Parameters

Cursors are opaque. Do not build or parse them, and do not reuse one with different filters. Each list’s filters, such as status, talent or created_after, are on its reference page.

Read every page

Read a feed

The revocation feed and the events list take after. Store the ID of the last item you processed, and pass it as after on the next read. Items come oldest first. When has_more is true, read again with after set to the last ID in data. Before your first read you have no ID: Handling revocations shows where to start.
If your platform caches decisions, read the revocation feed at least every 60 seconds. Webhooks are the fast path; the feed is the source of truth. See Handling revocations. The events list covers the last 30 days. To recover from a webhook outage, read it with after set to the last event you processed. See Webhooks.

Introduction

The objects and the conventions every endpoint shares.

Rate limits

Limits per account, and the headers that report them.