Attendees API
The attendees endpoint gives you the distinct people who have ordered across all of your organisation's events: one row per person, with how many orders they have placed and whether they have consented to marketing. It is the natural feed for syncing a CRM or mailing list. Requires the read scope.
| Method | Path | Returns |
|---|---|---|
| GET | /v1/attendees | A paginated list of distinct attendees for your organisation. |
curl "https://developer.seaty.co.uk/v1/attendees?per_page=100" \
-H "Authorization: Bearer sk_live_your_key_here"
| Field | Type | Description |
|---|---|---|
email | string | The attendee's email address. |
attendee_name | string | null | Their name, where known. |
order_count | integer | How many orders they have placed across your events. |
allow_marketing | boolean | Whether they have consented to marketing. |
member_email | string | null | The linked member email, if they are an organisation member. |
Respecting consent
Use allow_marketing to decide who you may contact for marketing. Only sync contacts to a mailing list where allow_marketing is true, and keep your list in step with Seaty so that anyone who later withdraws consent is removed. You remain the data controller for any contacts you export; handle them in line with UK GDPR.
Walking the full list
There can be many attendees, so page through with a large per_page and follow links.next until it is null:
# page 1
curl "https://developer.seaty.co.uk/v1/attendees?page=1&per_page=100" \
-H "Authorization: Bearer sk_live_your_key_here"
# then page 2, 3, ... while links.next is not null
Remember the read rate limit of 60 requests per minute, so add a small pause between pages if you are pulling a large list.
Next
- Requests and responses: pagination and rate limits in detail.
Need help? Email support@seaty.co.uk.