Skip to main content
POST
/
api
/
v1
/
inbox
/
threads
/
{reply_id}
/
reply
curl -X POST "https://api.foxreach.io/api/v1/inbox/threads/rpl_abc123/reply" \
  -H "X-API-Key: otr_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "body": "Thanks for your interest, John! I'\''d love to schedule a quick call. Does Thursday at 2pm work?"
  }'

{
  "data": {
    "success": true,
    "messageId": "<[email protected]>"
  }
}

​
Path Parameters

​
reply_id
string
required
The unique identifier of the reply thread to respond to.

​
Body Parameters

​
body
string
required
The reply message body (plain text or HTML).
​
subject
string
Optional subject line override. Defaults to Re: <original subject>.

​
Response

​
data
object
curl -X POST "https://api.foxreach.io/api/v1/inbox/threads/rpl_abc123/reply" \
  -H "X-API-Key: otr_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "body": "Thanks for your interest, John! I'\''d love to schedule a quick call. Does Thursday at 2pm work?"
  }'

{
  "data": {
    "success": true,
    "messageId": "<[email protected]>"
  }
}

​
Errors

StatusDescription
400Reply body is required
404Thread not found
500Failed to send reply (SMTP error)

​
Rate Limit

  • 100 requests per minute, per API key. Fixed 60-second window.
  • Every response includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset (unix epoch seconds).
  • A 429 response includes a Retry-After header (seconds until the bucket resets).
For client-side patterns (Retry-After, exponential backoff, monitoring X-RateLimit-Remaining), see Rate Limiting.