Skip to main content
POST
Check for overlapping scheduled campaigns

Authorizations

Authorization
string
header
required

Dashboard JWT token from Clerk

Body

application/json
scheduled_at
string<date-time>
required

Proposed send time (ISO 8601) to check conflicts around.

channel
enum<string>
required

Channel to scope the conflict scan to.

Available options:
sms,
mms,
whatsapp,
email,
rcs,
viber,
voice,
push,
instagram,
messenger,
line,
telegram,
fax,
kakao,
zalo,
wechat
audience_type
enum<string>
default:all

How the campaign's audience is selected.

Available options:
all,
list,
segment,
csv,
manual
audience_id
string

List or segment id the campaign targets, when applicable.

Required string length: 1 - 128
window_hours
integer

Half-window (in hours) around scheduled_at to scan. Defaults to 72; capped at 720 (30 days).

Required range: 1 <= x <= 720
exclude_campaign_id
string

Campaign id to exclude so an edited campaign doesn't conflict with itself.

Required string length: 1 - 128

Response

200 - application/json

Overlapping campaigns near the proposed send time

Overlapping campaigns near the proposed send time

data
object
meta
object