Attach a sender to a program
Assign a mailbox the program can send from (a program needs at least one to launch).
Authorizations
Org-scoped Norbelys API key. Create one in Settings → API keys and send it as Authorization: Bearer ak_….
Headers
Opt-in idempotency for a safely retried write: reuse the same key to replay the original result for 24h instead of re-executing. Recommended on every POST.
255Path Parameters
The program id.
Body
The sender to attach.
Response
OK
The sender's from address.
The sender's display name.
"Ada from Acme"
The sender id.
"snd_pfh0haxfpzowht3oi213cqos"
The mailbox's own daily send ceiling. Carried here so a caller can render the fleet without a second lookup.
x >= 050
Minimum minutes between two sends from this mailbox.
x >= 06
When this mailbox's next scheduled send in this program is due (RFC 3339), or null. A past instant means it is due now and goes out on the mailbox's next turn. Accounts for BOTH the threads this mailbox owns and the shared pool it can pull from — a mailbox with pool work due is 'now', never the date of its own far-off follow-up.
Leads due in this program's SHARED pool — not owned by any mailbox, so every attached mailbox can pull from them. The same number repeats on every row of the list: it is the campaign's backlog, not this mailbox's.
x >= 09814
Active leads whose thread this mailbox owns and that still have a send scheduled in this program. Only present in list responses.
x >= 012
Latest reputation verdict for the mailbox, when known.
"good"
The mailbox's operational state (healthy / throttled / paused).
"healthy"
How the mailbox is attached: manual (explicit attach) or tag (matched by the campaign's senderTags selector — detach it by changing the tags, not by remove).
manual, tag "tag"