Skip to content

Activate Engagers

POST
/radar/competitors/{competitor_id}/engagers/activate

Add a rival’s known engagers to an existing list, or enroll them in a LIVE or WAITING sequence.

enroll_sequence adds them to the sequence’s bound list and syncs at once, so they can be contacted by that sequence: it needs the sequence-write scope as well. Every contact id is checked against the rival’s current engager set (404 naming the strangers, nothing added). The app’s list-write, contact-write and rep-limit checks all run: a rep-limit conflict answers 409 CONFLICT_REVIEW_REQUIRED and is resubmitted with conflict_resolution (and include_warned_ids), exactly as in the app. Preview first with .../activate/preview.

Authorizations

Parameters

Path Parameters

competitor_id
required

Competitor id (from GET /radar/competitors).

string

Competitor id (from GET /radar/competitors).

Header Parameters

X-Target-Org-Id
Any of:
string

Request Body required

object
action
required
string
Allowed values: add_to_list enroll_sequence
conflict_resolution
Any of:
string
Allowed values: add_all skip_all custom
contact_ids
required
Array<integer>
>= 1 items
destination_list_id
Any of:
integer
destination_list_name
Any of:
string
include_warned_ids
Any of:
Array<string>
sequence_id
Any of:
string

Responses

200

Successful Response

422

Validation Error

object
detail
Array<object>
object
loc
required
Array
msg
required
string
type
required
string