outreach

Reject every ticked task

The queue's bulk reject, over the rows a person ticked. A reason, when one is given, covers the batch and is kept on every row it settled as its note; the Tasks page sends none. A bulk rejection teaches the agent nothing: only a single rejection is the person's Needs work on the agent's words. As with a single rejection this is a judgement about the contact, not the step: the engine stops each of them when it next sweeps. Rows that are no longer waiting on a person are skipped.

post/outreach-tasks/bulk/reject/

Request

  • Base URL: https://api.getoneprofile.ai (the document declares no server; this is the origin it was published from)
  • URL: https://api.getoneprofile.ai/outreach-tasks/bulk/reject/
  • Auth: one of:
    • API key in header X-API-Key
    • HTTP bearer

Request body

reasonstring nullable

Why they were refused, kept on every task it settled as its note. A bulk rejection teaches the agent nothing; the Tasks page sends no reason with one.

task_idsstring[] required

Response

Successful Response

decidedinteger required

How many rows the decision applied to.

skippedinteger required

How many had already moved on (settled, decided by somebody else, or a task nobody approves), and how many LinkedIn steps LinkedIn could not take now (the sender is not connected), which still wait. Not an error: a selection goes stale while it is read.

Changes

No recorded changes to this operation across all 1 revision of this API.