List connected sending accounts
The mailboxes and LinkedIn accounts this org sends outreach through. Never includes a provider credential — Bellwork holds only an opaque account handle. Gated by the `sequencer` module.
The mailboxes and LinkedIn accounts this org sends outreach through. Never includes a provider credential — Bellwork holds only an opaque account handle. Gated by the sequencer module.
API key (sk_live_... prefix). Generate keys in the UI under Settings > API Keys, then send it as Authorization: Bearer sk_live_...
In: header
Response Body
application/json
application/json
application/json
curl -X GET "https://loading/api/v1/org/mailboxes"{
"data": [
{
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"provider": "GOOGLE",
"display_name": "string",
"email_address": "string",
"status": "connecting",
"daily_send_cap": -9007199254740991,
"daily_invite_cap": -9007199254740991,
"connected_at": "string",
"owner_profile_id": "21e0f360-ea66-4de2-b817-b59c51592556"
}
]
}{
"error": "string",
"message": "string",
"statusCode": -9007199254740991
}{
"error": "module_required",
"module": "string",
"message": "string",
"contact": "string"
}List drafts written from a template GET
Every saved draft that followed this template, newest first — the read behind the usage count on the Templates page. Org-scoped twice over: the template must belong to the caller's org, and drafts are constrained to the org's member profiles (generated_emails carries no org_id).
Start connecting an account POST
Mints a one-time link to the hosted sign-in page where the customer connects Gmail, Outlook, an IMAP mailbox, or LinkedIn. The sign-in happens entirely off Bellwork, so no password or provider token reaches us; the account appears in the list once the callback lands. Minted fresh every time and never stored — these links expire on a daily restart whatever the stated expiry says, so a saved one silently stops working.