admin
campaigns

Schedule Gaps

Day × Org × Campaign gaps: campaigns expected to send but with no send that day.

A gap is a past org-local day a campaign was live + CRON-scheduled + its cron fired, yet produced no campaign_send row. Historical active/cron state is reconstructed from agent.edit_log. Cross-org by default; pass organization_id to scope. Same default-7-day window + 31-day cap as sends-by-day. Only past complete days are evaluated — the current day is never flagged.

get/admin/campaigns/schedule-gaps

Request

  • Base URL
    https://api-docs.upsmith.com (the document declares no server; this is the origin it was published from)
  • Auth
    • API key in header x-api-key
    • or HTTP bearer

Query parameters

organization_idstring nullable
start_datestring date nullable
end_datestring date nullable

Headers

organization-idstring nullable
timezonestring
x-user-idstring nullable
x-actor-emailstring nullable
x-request-sourcestring nullable
x-operation-idstring nullable
x-commit-messagestring nullable
x-confirmation-idstring nullable
x-chat-idstring nullable

Response

Successful Response

daystring date required
organization_idstring required
organization_namestring nullable
campaign_idstring required
campaign_slugstring required
cron_schedulestring required

Changes

No recorded changes to this operation across all 2 revisions of this API.