Skip to main content
POST
/
api
/
replies
/
{id}
/
forward
Forward Reply
curl --request POST \
  --url https://api.example.com/api/replies/{id}/forward \
  --header 'Content-Type: application/json' \
  --data '
{
  "to": [
    {}
  ],
  "message": "<string>",
  "include_thread": true
}
'
{
  "data": {
    "success": true,
    "forwarded_to": [
      {}
    ],
    "forwarded_at": "<string>"
  }
}
Forward the reply content to one or more email addresses. Useful for escalating leads or sharing with team members outside of Replyify.

​
Path Parameters

​
id
string
required
The unique identifier (UUID) of the reply

​
Request Body

​
to
array
required
Array of email addresses to forward to
​
message
string
Optional message to include above the forwarded content
​
include_thread
boolean
default:"true"
Whether to include the full email thread in the forward

​
Response

​
data
object
Forward confirmation

​
Examples

​
Basic Forward

curl -X POST "https://app.replyify.ai/api/replies/abc123-def456-ghi789/forward" \
  -H "Authorization: Bearer rpl_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "to": ["sales@yourcompany.com"]
  }'

​
Forward with Message

curl -X POST "https://app.replyify.ai/api/replies/abc123-def456-ghi789/forward" \
  -H "Authorization: Bearer rpl_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "to": ["sales@yourcompany.com", "manager@yourcompany.com"],
    "message": "Hot lead - please follow up ASAP. They are interested in our enterprise plan.",
    "include_thread": true
  }'

​
Response Example

{
  "data": {
    "success": true,
    "forwarded_to": [
      "sales@yourcompany.com",
      "manager@yourcompany.com"
    ],
    "forwarded_at": "2024-01-15T17:00:00Z"
  }
}

​
Errors

​
400 Bad Request
{
  "error": "At least one recipient email is required"
}
The to array is empty or missing.
​
400 Bad Request
{
  "error": "Invalid email address: invalid-email"
}
One or more email addresses in the to array are invalid.
​
404 Not Found
{
  "error": "Reply not found"
}
The specified reply ID doesn’t exist in your workspace.

​
Notes

Forwarding a reply triggers the reply.forwarded webhook event if you have webhooks configured.
Forwarding does not change the reply’s status. You can still send a response to the original sender after forwarding.