Bulk Update Threads
Set read, starred or category on up to 100 threads in one call.
https://api.foxreach.io/ api/ v1/ inbox/ threads/ bulk-updateRequires an API key with the write scope.
Ids that are not in this workspace are skipped and not counted. Fields you leave out, or send as null, are not changed. Setting category to unsubscribe unsubscribes each affected lead and cancels their queued sends in every campaign; that cannot be undone. A category change writes an audit entry per thread and fires the reply.categorized webhook event.
Body Parameters#
idsstring[]bodyrequiredThread identifiers, 1 to 100.
isReadbooleanbodyMark read or unread.
isStarredbooleanbodyStar or unstar.
categorystringbodyNew category. One of: interested, not_interested, out_of_office, bounce, unsubscribe, uncategorized, unknown, unrelated.
Response#
Returns { "data": { "updated": 2 } }, the number of threads found in this workspace.
Errors#
| Status | Description |
|---|---|
401 | Missing, invalid, revoked or expired API key |
403 | API key does not have the required scope: write |
422 | ids is empty or has more than 100 items, no field to change, or an unknown category |
Rate Limit#
- 100 requests per minute, shared by every
bulkcall in your workspace. Fixed 60-second window. - Every response includes
X-RateLimit-Limit,X-RateLimit-Remaining,X-RateLimit-Reset(unix epoch seconds) andX-RateLimit-Bucket(bulk). - A
429response includes aRetry-Afterheader (seconds until the bucket resets).
For client-side patterns, see Rate Limiting.