Forward the reply content to one or more email addresses. Useful for escalating leads or sharing with team members outside of Replyify.
Path Parameters
The unique identifier (UUID) of the reply
Request Body
Array of email addresses to forward to
Optional message to include above the forwarded content
Whether to include the full email thread in the forward
Response
Forward confirmation
Whether the forward was successful
List of email addresses the reply was forwarded to
ISO timestamp when the forward was sent
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": ["[email protected]"]
}'
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": ["[email protected]", "[email protected]"],
"message": "Hot lead - please follow up ASAP. They are interested in our enterprise plan.",
"include_thread": true
}'
Response Example
Errors
{
"error": "At least one recipient email is required"
}
The to array is empty or missing.
{
"error": "Invalid email address: invalid-email"
}
One or more email addresses in the to array are invalid.
{
"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.