A subscriber's events

The history of one subscriber, oldest first, a page at a time: the events about it (subscriber.*) since it was added. Events about the address and no subscriber (suppressions) are in list_suppressions. Needs scope read; an admin key may read any project’s. An erased subscriber has none to read (404).

Parameters

Name	In	Type	Description
`project_id`required	path	string · uuid	The project’s id
`subscriber_id`required	path	string · uuid	The subscriber’s id
`limit`	query	integer · int64 1–500	Page size, 1 to 500; default 50
`cursor`	query	string	`next_cursor` of the previous page

Request body

None.

Responses

200

One page

SubscriberEventList object · all fields required
itemsarray of Event

Oldest first: by time, then by event id.
7 fields
- Event object · all fields required
- event_idstring · uuid
- list_idstring · uuid | null
  
  The list the event is about; null for none.
- payloadobject
  
  What the event says, by type: plain values (strings, integers, booleans, null); actor_key_id is the key that acted.
- project_idstring · uuid
- subscriber_idstring · uuid | null
  
  The subscriber the event is about; null for none.
- tsstring · date-time
- typestring
  
  subscriber.created, subscriber.unsubscribed, subscriber.resubscribed, subscriber.reactivated, …
  
  example subscriber.created
next_cursorstring | null

Pass as cursor for the next page; null on the last page.

401

No valid key

Problem (application/problem+json)

403

A project key without scope read (forbidden)

Problem (application/problem+json)

404

No such subscriber or project, or another project’s (not_found)

Problem (application/problem+json)

422

A parameter is invalid (validation_failed)

Problem (application/problem+json)

429

The key is over its rate limit, api.rate_limit_per_minute requests a minute on this node (rate_limited)

Header	Type	Description
`Retry-After`	integer	Seconds until the key’s next request passes; rounded up.

Problem (application/problem+json)

504

Postwind’s storage did not answer within its time limit (storage_timeout). A change the request makes may still take effect: check before repeating it. A repeat with the same Idempotency-Key never runs it twice: it is 409 idempotency_key_in_progress until the key’s 24 h end

Problem (application/problem+json)