Skip to main content
POST
/
api
/
v1
/
campaigns
/
{campaign_id}
/
leads
/
{lead_id}
/
resume
curl -X POST "https://server.smartlead.ai/api/v1/campaigns/123/leads/456/resume?api_key=YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"resume_lead_with_delay_days": 3}'

{
  "ok": true,
  "data": "success"
}
Resuming a lead changes its status to INPROGRESS and schedules the next email based on the delay specified. If no delay is provided, the sequence’s default delay is used.

​
Path Parameters

​
campaign_id
number
required
The campaign ID containing the lead
​
lead_id
number
required
The lead ID to resume

​
Query Parameters

​
api_key
string
required
Your SmartLead API key

​
Request Body

​
resume_lead_with_delay_days
number
Number of days to wait before sending the next email. If not provided, uses the default delay from the sequence configuration. The next email timestamp is calculated as last_sent_time + delay_days.
curl -X POST "https://server.smartlead.ai/api/v1/campaigns/123/leads/456/resume?api_key=YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"resume_lead_with_delay_days": 3}'

​
Response Codes

​
200
Success
Lead resumed successfully
​
401
Unauthorized
Invalid or missing API key
​
404
Not Found
Campaign not found or you don’t have access to it
​
500
Internal Server Error
Server error occurred (e.g., lead is at the last sequence and cannot be resumed)
{
  "ok": true,
  "data": "success"
}

​
Behavior Notes

When a lead is resumed:
  • Lead status changes from PAUSED to INPROGRESS
  • The next sequence is determined automatically
  • The next_timestamp_to_reach is calculated based on:
    • If resume_lead_with_delay_days is provided: last_sent_time + specified_days
    • If not provided: Uses the default delay from the sequence configuration
    • If no last_sent_time exists: Scheduled immediately (NOW)
  • Drafted emails are marked as DRAFTED and ready to send
You cannot resume a lead that is already on the last sequence of the campaign. Attempting to do so will return an error.