List contacts
Lists contacts newest-first. Filter by tag; page with limit + before. Requires a write-scope key.
bearerAuth writeAuthorizationBearer <token>An API key from the dashboard under Settings → API keys, sent as Authorization: Bearer aem_….
Authorization has two independent axes.
The scope is ranked — a key satisfies any requirement at or below its own tier:
read— see messages, contacts and metrics. Changes nothing, and cannot send.write— everythingreaddoes, plus managing templates, contacts, automations, segments and suppressions. This is what editing a template needs.admin— everythingwritedoes, plus sending configuration: domains, senders, webhook registration, kill switch, daily cap, brand.
There is no approve scope. It was a rung once; it is not one now, and a key requested with it is rejected.
The approval grant (can_approve) is a separate boolean, not a rung. Delivering mail to a real inbox needs write and the grant. Keeping them on separate axes is what makes the review gate a control rather than a convention: a key that may propose is not automatically a key that may approve its own proposal.
Give your application the lowest tier that works. Most need write and the grant — the dashboard mints that combination as Send + manage; Manage only is the same rung with the grant withheld.
Scope: write
tag?stringOnly contacts carrying this tag.
limit?integerPage size (1–100, default 50).
before?stringDeprecatedDeprecated — use cursor. ISO 8601 created_at: rows older than this.
cursor?stringOpaque — pass the previous page's next_cursor to fetch the next page. A malformed cursor is refused, never treated as page one.
A page of contacts.
application/json- response
data*array<>has_more*booleanMore rows exist after this page.
object*"list""list"next_cursor*|Pass as ?cursor= for the next page. Null on the last page.
curl -X GET 'https://sendandretain.com/api/v1/contacts?tag=vip&limit=50'{ "data": [ {} ], "has_more": true, "object": "list", "next_cursor": "string"}