Skip to main content
POST
Snooze tasks in bulk
Pushes up to 500 tasks to the same new due time, for example everything a rep could not reach before a day off.

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_at is 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 held tasks are listed in failed.
  • Snoozing is not recorded on task timelines.

Authorizations

x-api-key
string
header
required

Team-scoped API key generated in the Salesfinity dashboard under Settings → Connections → API & Webhooks. A missing or invalid key returns HTTP 403.

Headers

Idempotency-Key
string

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

application/json
user_id
string
required

The team member this call acts as. Must be an active member of the team the API key belongs to.

Example:

"507f1f77bcf86cd799439011"

ids
string[]
required

Task ids, 1 to 500. Each is processed on its own, and a failure is returned in failed.

Maximum array length: 500
due_at
string<date-time>
required

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

Response

How many tasks were snoozed, and which were not.

Per-task outcome of a bulk action.

ok
integer
required

Tasks the action succeeded on.

failed
object[]
required

Tasks it did not, each with the reason the single-task operation gave.