Skip to main content
POST
Reassign tasks in bulk
Moves up to 500 tasks to another rep, for example to cover someone who is out.

Handling the response

Good to know

  • Only the tasks move. Each prospect stays in its sequence under the same owner, and the next step’s task goes to that owner. To move prospects for good, reassign their enrollments.
  • user_id needs permission for each task: its assignee, the sequence’s owner, a team admin or, for a one-off task, whoever created it. Tasks it may not reassign are listed in failed.
  • Call tasks leave the old rep’s dial list and are queued for the new rep’s.

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
assignee_id
string
required

The team member to hand the tasks to. A non-member fails every task, each listed in failed.

note
string

Recorded on each reassignment timeline event.

Maximum string length: 500

Response

How many tasks were reassigned, 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.