Skip to main content
POST
/
api
/
v1
/
campaigns
/
{campaign_id}
/
schedule
curl -X POST "https://server.smartlead.ai/api/v1/campaigns/123/schedule?api_key=YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "schedule": {
      "timezone": "America/New_York",
      "days": [1, 2, 3, 4, 5],
      "start_hour": "09:00",
      "end_hour": "17:00",
      "min_time_btw_emails": 120
    }
  }'

{
  "success": true,
  "data": {
    "message": "Schedule updated successfully",
    "schedule": {
      "timezone": "America/New_York",
      "days_of_week": [1, 2, 3, 4, 5],
      "start_time": "09:00",
      "end_time": "17:00",
      "min_time_between_emails": 120
    }
  }
}
Configures when and how frequently campaign emails are sent Sets timezone (IANA format), sending hours (start/end in 24-hour format), active days of week (0=Sunday through 6=Saturday), and minimum time between consecutive emails (in minutes)

​
Overview

Configures when and how frequently campaign emails are sent Key Features:
  • Validates timezone string and time format before saving

​
Path Parameters

​
campaign_id
number
required
The ID of the campaign to update

​
Query Parameters

​
api_key
string
required
Your SmartLead API key

​
Request Body

​
schedule
object
required
Sending schedule configuration
curl -X POST "https://server.smartlead.ai/api/v1/campaigns/123/schedule?api_key=YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "schedule": {
      "timezone": "America/New_York",
      "days": [1, 2, 3, 4, 5],
      "start_hour": "09:00",
      "end_hour": "17:00",
      "min_time_btw_emails": 120
    }
  }'

​
Response Codes

​
200
Success
Request successful
​
400
Bad Request
Invalid request parameters or malformed request body
​
401
Unauthorized
Invalid or missing API key. Check your authentication.
​
404
Not Found
The requested resource (campaign, lead, email account, etc.) does not exist or you don’t have access to it
​
422
Validation Error
Request validation failed. Check parameter types, required fields, and value constraints.
​
429
Rate Limit Exceeded
Too many requests. Please slow down and retry after the rate limit resets.
​
500
Internal Server Error
Server error occurred. Please try again or contact support if the issue persists.
​
503
Service Unavailable
API is temporarily unavailable or under maintenance. Please try again later.
{
  "success": true,
  "data": {
    "message": "Schedule updated successfully",
    "schedule": {
      "timezone": "America/New_York",
      "days_of_week": [1, 2, 3, 4, 5],
      "start_time": "09:00",
      "end_time": "17:00",
      "min_time_between_emails": 120
    }
  }
}

​
Schedule Best Practices

​
Business Hours

Send during recipient’s business hours:
  • B2B: 9 AM - 5 PM local time
  • B2C: 10 AM - 8 PM local time
  • Global: Consider multiple timezones

​
Days of Week

Monday-Friday [1,2,3,4,5]  - Best for B2B
Tuesday-Thursday [2,3,4]    - Highest open rates
All 7 days [0,1,2,3,4,5,6] - For B2C or urgent campaigns

​
Time Between Emails

  • 120+ minutes: Appears more natural
  • 60-120 minutes: Moderate pacing
  • 30-60 minutes: Aggressive (use carefully)
Longer delays between emails (2-3 hours) result in better deliverability and appear more natural to recipients.

​
Common Timezones

  • America/New_York - US Eastern
  • America/Los_Angeles - US Pacific
  • America/Chicago - US Central
  • Europe/London - UK
  • Europe/Paris - Central Europe
  • Asia/Tokyo - Japan
  • Asia/Dubai - UAE
  • Asia/Kolkata - India
  • Australia/Sydney - Australia
See full list of timezones

​
Implementation Details

Schedule timezone must be valid IANA timezone. Start/end hours in 24-hour format. Min time between emails prevents rapid-fire sending. Response Format: object