Skip to main content
POST
Events Calendar

Authorizations

X-API-KEY
string
header
required

Body

application/json
rp_entity_id

A list of RavenPack internal entity identifiers. Bigdata uses the RavenPack Entity identifier (RP_Entity_ID) to uniquely reference entities such as companies. This identifier is a 6-character alphanumeric code (letters and numbers only). Example: Alphabet Inc. (4A6F00)

Example:

"4A6F00"

start_date
string<date> | null

The start date of the time range for retrieving events. Only events occurring on or after this date will be included. The expected date format is 'YYYY-MM-DD'.

Example:

"2025-09-02"

end_date
string<date> | null

The end date of the time range for retrieving events. Only events occurring on or before this date will be included. The expected date format is 'YYYY-MM-DD'.

Example:

"2025-09-03"

countries

A list of country codes (ISO 3166-1 alpha-2) to filter events by country. If omitted, events from all countries will be returned. The IPO and delisted calendars cover US companies only, so 'ipos-calendar' and 'delisted-company' events are included when the country list is omitted or empty, or when 'US' is included in the list.

Example:

"US"

exchanges
string[] | null

Exchange code(s) to filter events by. Accepts MIC codes (ISO 10383, e.g. 'XNYS', 'XNGS'). Accepts a single exchange or a list. Setting this filter excludes 'ipos-calendar' and 'delisted-company' events from the response entirely - both report exchanges as free text rather than MIC codes, so neither can honour the filter.

Example:

"XNYS"

categories
enum<string>[] | null

A list of event categories to filter by. Events covered: 'earnings-call', 'conference-call', 'ipos-calendar', 'delisted-company'. IPO listings and delistings are US-only, and the 'cursor' and 'exchanges' filters do not apply to either. If omitted, every category your organization has access to is returned. Note that every delisting is in the past, so a forward-looking window matches none of them. 'delisted-company' covers delistings from 2025-01-01 onwards; naming it with an 'end_date' before that returns 422 rather than an empty calendar, and naming it without a 'start_date' returns every delisting from 2025-01-01 to your 'end_date'. Set 'start_date' to narrow that. Access to 'ipos-calendar' and 'delisted-company' is enabled per organization. A category your organization does not have is left out of the response and the rest of the request is served; a request left with no category to serve returns 403.

Available options:
earnings-call,
conference-call,
ipos-calendar,
delisted-company
Example:

"earnings-call"

cursor
string | null

The cursor for pagination. Use the 'cursor' value from the previous response's pagination to get the next set of results.

Example:

"375207"

limit
integer | null

The number of results to return per page. Must be between 1 and 1000, both inclusive. It bounds the transcript events a page pages through; IPO listings are returned alongside them, so a page can carry more events than the limit.

Required range: 1 <= x <= 1000
Example:

100

Response

200 - application/json

Successful Response

results
Results · object
required

A dictionary mapping RP entity IDs to lists of event calendar entries for each company. Only events whose company has an rp_entity_id appear here; the rest are in 'events_unmapped', so read both to get the whole calendar.

errors
ErrorDetail · object[] | null
metadata
Metadata · object | null
pagination
Pagination · object | null

Common pagination response for endpoints that support pagination.

events_unmapped
EventCalendar · object[] | null

Events whose company has not been mapped to an rp_entity_id appear here instead of in 'results'. For an IPO listing this reflects a temporary state in the mapping process: once the company begins trading and mapping completes, the event moves into 'results'. A delisted company may instead never have been mapped. Identify these events by 'ticker' and 'company_name'.