How many people are waiting to be reviewed
One number, for a badge. Answers 0 rather than 403 for an org without the sequencer, so a caller that asks on every page does not have to know whether the module is on.
One number, for a badge. Answers 0 rather than 403 for an org without the sequencer, so a caller that asks on every page does not have to know whether the module is on.
API key (sk_live_... prefix). Generate keys in the UI under Settings > API Keys, then send it as Authorization: Bearer sk_live_...
In: header
Response Body
application/json
application/json
curl -X GET "https://loading/api/v1/org/outreach-queue/count"{
"data": {
"toReview": -9007199254740991
}
}{
"error": "string",
"message": "string",
"statusCode": -9007199254740991
}Approve many people at once POST
Everyone waiting in one sequence, or a chosen few. Sends nothing by itself: each approved person is handed to the clock, and the sending account's own limits space their messages out from there.
Approve or remove one person POST
`approve` hands this person's plan to the clock: the step they are standing on goes out in the sequence's sending hours, spaced by the account's limits, and every later step follows on schedule exactly as the plan was left. It does not send anything itself. `remove` takes them out of the sequence and nothing is ever sent. Keyed on the enrollment, so a second press finds it already dealt with and says so.