Skip to main content
PATCH
/
api
/
v1
/
inbox
/
threads
/
{reply_id}
curl -X PATCH "https://api.foxreach.io/api/v1/inbox/threads/rpl_abc123" \
  -H "X-API-Key: otr_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "isRead": true,
    "isStarred": true,
    "category": "interested"
  }'

{
  "data": {
    "id": "rpl_abc123",
    "fromEmail": "[email protected]",
    "toEmail": "[email protected]",
    "subject": "Re: Quick question about your product",
    "bodyPreview": "Hi, thanks for reaching out! I'd love to learn more about...",
    "category": "interested",
    "isRead": true,
    "isStarred": true,
    "receivedAt": "2025-01-20T14:30:00",
    "leadId": "cld_xyz789",
    "campaignId": "cmp_def456"
  }
}

​
Path Parameters

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

​
Body Parameters

​
isRead
boolean
Mark thread as read or unread.
​
isStarred
boolean
Star or unstar the thread.
​
category
string
Manually override the AI category. One of: interested, not_interested, out_of_office, uncategorized, unknown.

​
Response

Returns the updated thread object. 
curl -X PATCH "https://api.foxreach.io/api/v1/inbox/threads/rpl_abc123" \
  -H "X-API-Key: otr_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "isRead": true,
    "isStarred": true,
    "category": "interested"
  }'

{
  "data": {
    "id": "rpl_abc123",
    "fromEmail": "[email protected]",
    "toEmail": "[email protected]",
    "subject": "Re: Quick question about your product",
    "bodyPreview": "Hi, thanks for reaching out! I'd love to learn more about...",
    "category": "interested",
    "isRead": true,
    "isStarred": true,
    "receivedAt": "2025-01-20T14:30:00",
    "leadId": "cld_xyz789",
    "campaignId": "cmp_def456"
  }
}

​
Errors

StatusDescription
404Thread not found
422Invalid category value

​
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.