Reply to a conversation
Send a reply through the same connected account the sequencer sends from, so the district sees one continuous conversation. The reply is recorded on the timeline. A provider failure returns 502 rather than being retried — someone is watching, and a silent retry would either duplicate the message or look like nothing happened.
Send a reply through the same connected account the sequencer sends from, so the district sees one continuous conversation. The reply is recorded on the timeline. A provider failure returns 502 rather than being retried — someone is watching, and a silent retry would either duplicate the message or look like nothing happened.
API key (sk_live_... prefix). Generate keys in the UI under Settings > API Keys, then send it as Authorization: Bearer sk_live_...
In: header
Request Body
application/json
1 <= items <= 25"email" | "linkedin""linkedin_invite" | "linkedin_message"length <= 5001 <= lengthitems <= 10Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://loading/api/v1/org/communications/reply" \ -H "Content-Type: application/json" \ -d '{ "recipients": [ {} ], "channel": "email", "body": "string" }'{
"data": {
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08"
}
}{
"error": "string",
"message": "string",
"statusCode": -9007199254740991
}{
"error": "string",
"message": "string",
"statusCode": -9007199254740991
}{
"error": "module_required",
"module": "string",
"message": "string",
"contact": "string"
}{
"error": "string",
"message": "string",
"statusCode": -9007199254740991
}{
"error": "string",
"message": "string",
"statusCode": -9007199254740991
}People you can write to GET
The org's contacts, for the compose picker — name, title, district, and whether they can be reached by email or LinkedIn. Only reachable people are returned: someone with neither is a dead end dressed as a choice, and you would only find out after writing the message.
Pull recent mail now POST
Fetches recent messages for this org's connected mailboxes and records anything new. The inbox calls it on open, because neither path that normally delivers a reply — the provider webhook or the periodic sync — runs on a developer machine, and a fresh deployment would otherwise show an empty inbox until the first scheduled tick. Idempotent: everything dedupes on the provider's message id.