{
"id": "01a1f9f7-4e29-7288-94ec-0a18541ed11e",
"name": "My First Campaign",
"status": 1,
"campaign_schedule": {
"schedules": [
{
"name": "My Schedule",
"timing": {
"from": "09:00",
"to": "17:00"
},
"days": {
"0": true,
"1": true,
"2": true,
"3": true,
"4": true,
"5": false,
"6": false
},
"timezone": "Etc/GMT+12"
}
],
"start_date": "2025-09-25",
"end_date": "2025-09-25"
},
"timestamp_created": "2026-11-20T17:18:16.617Z",
"timestamp_updated": "2026-11-20T17:18:16.617Z",
"pl_value": 100,
"is_evergreen": false,
"sequences": [
{
"steps": [
{
"type": "email",
"delay": 2,
"variants": [
{
"subject": "Hello {{firstName}}",
"body": "Hey {{firstName}},<br/><br/>I hope you are doing well.",
"v_disabled": true
}
],
"delay_unit": "days",
"pre_delay": 2,
"pre_delay_unit": "days"
}
]
}
],
"email_gap": 10,
"random_wait_max": 10,
"text_only": false,
"first_email_text_only": false,
"email_list": [
"john@doe.com"
],
"daily_limit": 100,
"stop_on_reply": false,
"email_tag_list": [
"01a1f9f7-4e29-7288-94ec-0a19d2448e7a"
],
"link_tracking": true,
"open_tracking": true,
"stop_on_auto_reply": false,
"daily_max_leads": 100,
"prioritize_new_leads": false,
"auto_variant_select": {
"trigger": "click_rate"
},
"match_lead_esp": false,
"not_sending_status": 2,
"stop_for_company": false,
"core_variables": {},
"custom_variables": {},
"insert_unsubscribe_header": false,
"same_domain_sender_failover": false,
"allow_risky_contacts": false,
"disable_bounce_protect": false,
"limit_emails_per_company_override": {
"mode": "custom",
"daily_limit": 3,
"scope": "per_campaign"
},
"cc_list": [
"john@doe.com"
],
"bcc_list": [
"john@doe.com"
],
"organization": "01a1f9f7-4e29-7288-94ec-0a1a9c8b4070",
"owned_by": "01a1f9f7-4e29-7288-94ec-0a1b4f58cad8",
"created_by": "01a1f9f7-4e29-7288-94ec-0a1cecd185c5",
"ai_sdr_id": "01a1f9f7-4e29-7288-94ec-0a1d3f48984b",
"provider_routing_rules": [
{
"action": "send",
"recipient_esp": [
"all"
],
"sender_esp": [
"all"
]
}
]
}Campaign
This schema describes objects returned by the Campaign endpoints.
A campaign that can be sent to a list of recipients
Send a follow-up from another account on the same domain when the account that last emailed the lead has hit its daily sending limit or slow ramp limit. Off by default: the follow-up waits for that account. API only; null means off.
When on:
- A switch happens only when that account hits its daily sending limit or slow ramp limit, or is removed from the campaign. For any other reason, such as the gap between sends, the follow-up waits.
- The other account must be in this campaign and on the exact same domain.
mail.acme.comandacme.comare different domains. - The follow-up stays in the same email thread.
- Each lead gets emails from at most 2 accounts in this campaign, including subsequences. The account that emailed the lead most recently is tried first.
- Counting starts when you turn this on. The account that last emailed the lead is the first of the 2; earlier accounts do not count.
- If none of the lead's accounts can send, the follow-up waits. It does not use a third account or another domain, except in the cases below.
- For this campaign, the workspace setting "Sticky sending accounts for leads" is ignored.
Exceptions:
- If every account the lead can use was removed from the campaign, a sender is picked as usual. It may be on another domain and may start a new thread. This keeps the campaign from stalling.
- In rare cases a lead can get a third account: when the lead enters or leaves a subsequence, is moved or re-added to the campaign, when this setting is turned off and on again, or when a send is interrupted before it is confirmed.
Example:
false