Get all forwards by conversation
/v1/conversations/{id}/forwardsorg.permission.draft.readorg.user.draft.readThe API key or user must hold at least one of them. Legacy roles still work; prefer the others for new keys.
Retrieves all forwarded conversations based on the unique conversation ID.
To learn more, see Forwarding conversations in the Kustomer Help Center.
Conversation forwards
A forward sends a copy of an entire conversation by email to someone outside it, such as a vendor, a warehouse or another department. It starts as a draft and is sent when you give it a send time.
Agents forward a conversation from the agent desktop when someone who isn't on the thread needs the full history, for example a shipping partner who has to investigate a lost package. A forward belongs to one conversation and its customer, and it emails all of that conversation's messages to the addresses you choose. Forwards are listed on the conversation they came from.
Lifecycle
A forward works like a draft: you create it, adjust it, and then send it.
status |
Meaning |
|---|---|
draft |
Created without sendAt. Nothing has been sent, and you can still edit it. |
scheduled |
Has a sendAt and is waiting to go out. |
sent |
Sent. |
failed |
Sending failed. |
Include sendAt when you create the forward to send it, or create it without one and set sendAt later with PUT /v1/forwards/{id}. Kustomer validates the email fields when a forward is scheduled.
Key fields
channel is always email. to is a list of { email, name } recipients and from is the { email, name } sender, which should be one of your org's email accounts; GET /v1/outboundAccounts lists them. app picks the sending integration (gmail or postmark). subject, body and replyTo work as they do for an email draft; body is the text you add for the recipient. attachments adds files that you upload through the forward attachment endpoints.
Which endpoint to use
| To | Call |
|---|---|
| Forward a conversation by email | POST /v1/conversations/{id}/forwards |
| See every forward made from a conversation | GET /v1/conversations/{id}/forwards |
To read, edit or schedule a single forward after creating it, use GET and PUT /v1/forwards/{id}. Creating a forward needs the conversation-forward permission (org.permission.conversation_forward.create), and listing forwards needs draft read access.
Path parameters
Conversation ID.
"5faaf4a6ea0cb48cd0801bbf"Responses
OK