Retrieve Calendar Events

Returns a paginated list of calendar events used to schedule Updates and Dedicated Offers. When filter_date is provided, returns events within a 4-month window (2 months before and after the date).

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
integer

Filter by event ID

string

Filter by event name

string

Filter by description

integer

Filter by publication ID

integer

Filter by calendar event category ID

string

Filter by start date. Supports operators: >, >=, <, <=

string

Filter by end date. Supports operators: >, >=, <, <=

string

Center date for a 4-month window (2 months before and after). Defaults to current date when not provided.

string

Filter by creation date. Supports operators: >, >=, <, <=

string

Filter by last updated date. Supports operators: >, >=, <, <=

status
array of strings

Filter by message status. placeholder: an email Update with no author or article; assigned: an author but no article; needs_content: a lift letter or SMS with no content; needs_ads: content is attached but an ad slot has no ad assigned; the rest are states of the built message. Ready and incomplete depend on resolved defaults, so read them from the event's message.

status
boolean

Only events whose message still needs its article, lift letter, or SMS text (true), or only those that have it (false). Before their message is saved, SMS events and email Updates count as missing, and email Dedicated Offers do unless they already name a lift letter.

boolean

Only events with (true) or without (false) a built message

string

Only events whose content is due on or before this wall-clock date-time

integer

Only events assigned to this user directly or through one of their groups

integer

Only events whose data names this author (the publication author ID)

integer

Only events whose message uses this article or lift letter in any variant

boolean

Add message_state to each event: status (placeholder, assigned, needs_content, needs_ads, in_progress, or a built state: pending_approval, approved, denied, cancelled, sent), overdue, out_of_sync, needs_reschedule, and issues (what someone still has to do, one line each: the missing list saved the last time the event's message was checked, or else one denial, rebuild, or reschedule note), and missing_count (how many of the issues are missing items; 0 when the only issue is a note). Built from stored state; in_progress means nothing stored blocks the message, and whether it is ready comes from get_calendar_event_message.

columns[]
array of strings

The field names to be included in the JSON response. You can have multiple columns[] query params included in the request URL (e.g. columns[]=id&columns[]=name).

columns[]
integer

The page to return.

integer

The total results to return per page.

string

The field to sort the request by. column_name|asc OR desc

Response

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Choose an example:
application/json