Re-queue leads blocked on our side
curl --request POST \
--url https://api.salessequencer.com/api/v1/campaigns/{campaign_id}/leads/requeue-sender-blocked \
--header 'X-API-Key: <api-key>'import requests
url = "https://api.salessequencer.com/api/v1/campaigns/{campaign_id}/leads/requeue-sender-blocked"
headers = {"X-API-Key": "<api-key>"}
response = requests.post(url, headers=headers)
print(response.text)const options = {method: 'POST', headers: {'X-API-Key': '<api-key>'}};
fetch('https://api.salessequencer.com/api/v1/campaigns/{campaign_id}/leads/requeue-sender-blocked', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));Leads
Re-queue leads blocked on our side
Every lead in the campaign with status sender_blocked (a failed delivery caused by our sending side: the provider refused to send, our SPF/DKIM/DMARC failed, or our IP/domain reputation was blocked) goes back to pending: one sequence step back so the failed step is sent again, due now, bounce fields and sender_originated cleared. Real recipient bounces (status bounced) are not touched. Does not launch or resume the campaign. 404 if the campaign is not in the workspace.
Minimum role: edit (x-min-role). Destructive: false (x-destructive).
POST
/
campaigns
/
{campaign_id}
/
leads
/
requeue-sender-blocked
Re-queue leads blocked on our side
curl --request POST \
--url https://api.salessequencer.com/api/v1/campaigns/{campaign_id}/leads/requeue-sender-blocked \
--header 'X-API-Key: <api-key>'import requests
url = "https://api.salessequencer.com/api/v1/campaigns/{campaign_id}/leads/requeue-sender-blocked"
headers = {"X-API-Key": "<api-key>"}
response = requests.post(url, headers=headers)
print(response.text)const options = {method: 'POST', headers: {'X-API-Key': '<api-key>'}};
fetch('https://api.salessequencer.com/api/v1/campaigns/{campaign_id}/leads/requeue-sender-blocked', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));