{ "opencollection": "1.0.0", "info": { "name": "Kit Accounts Broadcasts API", "version": "4.0" }, "items": [ { "info": { "name": "Broadcasts", "type": "folder" }, "items": [ { "info": { "name": "List broadcasts", "type": "http" }, "http": { "method": "GET", "url": "https://api.kit.com/v4/broadcasts", "params": [ { "name": "after", "value": "", "type": "query", "description": "To fetch next page of results, use `?after=`" }, { "name": "before", "value": "", "type": "query", "description": "To fetch previous page of results, use `?before=`" }, { "name": "include_total_count", "value": "false", "type": "query", "description": "Set to `true` to include the `total_count` in the response. This option can cause slow responses; if paging through results, request it only on the first page and reuse the value for subsequent pages." }, { "name": "per_page", "value": "", "type": "query", "description": "Number of results per page. Default 500, maximum 1000." }, { "name": "sent_after", "value": "", "type": "query", "description": "Get broadcasts sent after this date (format yyyy-mm-dd)." }, { "name": "sent_before", "value": "", "type": "query", "description": "Get broadcasts sent before this date (format yyyy-mm-dd)." }, { "name": "slim", "value": "false", "type": "query", "description": "When `true`, omits expensive optional fields from the response. Produces a faster, smaller response — useful when extra fields are not needed." } ], "auth": { "type": "apikey", "key": "X-Kit-Api-Key", "value": "{{X-Kit-Api-Key}}", "placement": "header" } }, "docs": "List broadcasts" }, { "info": { "name": "Create a broadcast", "type": "http" }, "http": { "method": "POST", "url": "https://api.kit.com/v4/broadcasts", "body": { "type": "json", "data": "{}" }, "auth": { "type": "apikey", "key": "X-Kit-Api-Key", "value": "{{X-Kit-Api-Key}}", "placement": "header" } }, "docs": "Draft or schedule to send a broadcast to all or a subset of your subscribers.

To save a draft, set `send_at` to `null`.

To publish to the web, set `public` to `true`.

To schedule the broadcast for sending, provide a `send_at` timestamp. Scheduled broadcasts should contain a subject and your content, at a minimum.

We currently support targeting your subscribers based on segment or tag ids.