Snooze tasks in bulk
Moves up to 500 tasks to the same due_at, one at a time, with the rules of POST /v2/sequencer/tasks/{id}/snooze.
Each task’s auto-skip deadline moves by the same amount as its own due date. A task that cannot be snoozed (already resolved, held, or not on the team) is listed in failed with the reason, and ok counts the rest. due_at must still be in the future when each task is processed.
Acts as user_id. Safe to replay: snoozing to the same due_at again changes nothing. Counts against the Sequencer writes rate limit.
Handling the response
Good to know
- Every task gets the same
due_at, and each task’s auto-skip deadline moves by that task’s own shift. due_atis checked as each task is processed. A time only seconds away can pass partway through and fail the remaining tasks, so leave a margin.- Resolved and
heldtasks are listed infailed. - Snoozing is not recorded on task timelines.
Authorizations
Team-scoped API key generated in the Salesfinity dashboard under Settings → Connections → API & Webhooks. A missing or invalid key returns HTTP 403.
Headers
Makes this write safe to retry. Send a unique value, such as a UUID, and send the same value again when you retry the same request. A retry with the same key and the same request (method, path including the query string, and JSON body) returns the original successful response without acting twice. The same key with a different body or path returns 409, and so does a retry while the first request is still running; that one is safe to repeat after a moment. A request that fails frees its key, so a retry runs the write again: after a 5xx on a create, confirm with a GET before retrying. Keys are kept for 24 hours and are scoped to your team.
Body
The team member this call acts as. Must be an active member of the team the API key belongs to.
"507f1f77bcf86cd799439011"
Task ids, 1 to 500. Each is processed on its own, and a failure is returned in failed.
500New due time for every task in ids, at most 365 days ahead. Must still be in the future when each task is processed; a task processed after it has passed fails with due_at must be in the future.