Radar

Activate Engagers

Changed on

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.

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

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/radar/competitors/{competitor_id}/engagers/activate
  • Auth: HTTP bearer

Path parameters

competitor_idstring required

Competitor id (from GET /radar/competitors).

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Request body

contact_idsinteger[] required
action'add_to_list' | 'enroll_sequence' required
destination_list_idinteger nullable
destination_list_namestring nullable
sequence_idstring nullable
conflict_resolution'add_all' | 'skip_all' | 'custom' nullable
include_warned_idsstring[] nullable

Response

Successful Response

unknown required

Changes