List claims originated for an entity
GET/claims
Lists the claims this partner originated for the given entity, newest first, with cursor pagination. Listing is most useful for reconciliation and is permitted even after the entity has disconnected the partner, so you can still reconcile historical claims; the disconnected state is surfaced via entity_disconnected / entity_disconnected_at at both the top level and on each claim.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 429
- 500
- 503
The matching claims.
The entity_id query parameter is missing, or page_token does not refer to a claim in this listing.
Authentication failed. The code distinguishes the cause: auth_missing (no Authorization header), auth_invalid_format (malformed token), auth_unknown_partner (no such partner), auth_revoked (partner or key revoked), auth_bad_secret (bad key id or secret).
The partner does not have access to this entity.
The referenced entity does not exist.
The per-partner rate limit (120 requests per minute, shared across all partner endpoints) was exceeded. Inspect Retry-After and the X-RateLimit-* headers before retrying.
Response Headers
Seconds to wait before retrying.
The request ceiling for the window.
Requests remaining in the current window.
Unix epoch milliseconds when the window resets.
An unexpected server error occurred. The message is always the generic string Internal error; key on code, not message.
A dependency the request relies on is temporarily unavailable. The partner did nothing wrong; retry after the delay in Retry-After.
Response Headers
Seconds to wait before retrying.