Approve a lead
Accepts the lead for its campaign, like Approve in the app: readyForCampaign is set to true and it leaves the review queue (review=to_review on GET /v1/contact). Use it on review-mode campaigns (isManual=true), where leads are not contacted until approved; the campaign picks the lead up at its next launch. Approving a rejected lead also clears its rejection (rejectedAt, rejectedByUserId and the reason), so no unreject call is needed first. When the lead belongs to a review-mode campaign and a connected CRM integration is set to send every lead, the lead is also queued for sync to that CRM, unless it was already synced there. The sync runs in the background: the response does not wait for it, and a failure to queue it does not fail the approval. Approving an already-approved lead keeps it approved. To take an approved lead out of the campaign, reject it with POST /v1/contact//reject.
Headers
Response
The approved contact, with readyForCampaign true and the rejection fields cleared
Whether the contact can be enrolled in the campaign. On a manual campaign (isManual=true), false with no rejectedAt means the contact is in review: the user must review and accept it before the agent adds it. A contact with rejectedAt set is rejected whatever this flag says. On an automatic campaign (isManual=false), the agent sets it to true itself when the contact is needed.
Campaign status information. Useful to know what is the achieved step of the contact in the campaign — i.e. how far the contact has progressed through the campaign's sequence. The stepNumber matches the campaign's step numbers (the steps defined on the campaign), so a stepNumber of 2 means the contact has reached step 2 of that campaign.
.png?fit=max&auto=format&n=fLzJlZyi7L0nfF9B&q=85&s=7dc539f8ea9f771a09a9750c1227ebdb)
.png?fit=max&auto=format&n=fLzJlZyi7L0nfF9B&q=85&s=e742bcbb4bd47cd295da36c48cdd6089)