Concepts
Approval
How a campaign is held for review before it sends.
A campaign moves through these states: draft, submitted, approved, scheduled, then sending and sent. A person or a rule moves it from submitted to approved.
Who needs approval#
- A store's campaigns are always reviewed. An AI review reads only the content (title, body, whether there is an image, the kind of destination) and answers approve, flag or reject. Depending on the store's trust tier, a flagged or unclear campaign goes to a person. Green and official stores are approved on a clean AI review, with a 5 percent spot check by a person. An AI rejection can be overridden only by a person.
- A workspace's own campaigns go straight to
approvedwhen submitted, unless the workspace turned on second approval (secondApprovalinPUT /v1/workspace/campaign-settings). Then a person who did not write the campaign must approve it, and the AI never does.
Deciding#
Reviewers decide in the console (Review) or from a Lark card sent to the workspace's reviewer group. A decision is approve, reject or ask for changes. Reject and ask for changes need a note, which the author reads. A decision names the content version the reviewer saw. If the content changed since, the answer is 409 stale_review.
Decisions are made by a person with an operator session and the reviewer role or above. API keys cannot decide, so a leaked key cannot push content past review.
Reading the queue#
GET /v1/review-queue lists campaigns waiting for a person, oldest first. GET /v1/reviews/{broadcastId} shows a campaign with its history and every review.
Refused at submit#
POST /v1/broadcasts/{id}/submit answers 409 send_refused when a kill switch is on or the store cannot send, with the reasons in details.reasons.