Worker queue health
Scheduling is ours, not the provider's: delayed sends, automation steps and throttle-deferred messages all wait in our queue. A growing pending_due_now or a large oldest_pending_age_seconds means mail is late; dead_letter means some gave up entirely. Worth alerting on.
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
Queue health.
application/json- response
pending_due_now?integeroldest_pending_age_seconds?integer|nullprocessing?integerdead_letter?integercurl -X GET 'https://sendandretain.com/api/v1/queue/health'{ "pending_due_now": 0, "oldest_pending_age_seconds": 0, "processing": 0, "dead_letter": 0}