Event Discovery API

event discovery api the event discovery api provides a read only endpoint for listing all events within a jomablue instance it is designed for third party systems such as crm platforms, marketing automation tools, or scheduling systems to programmatically discover events, their associated programs, and their ingest endpoint and updates endpoint urls endpoint get /integration/api/events authentication requests must include a valid instance level bearer token in the authorization header this is the same token generated when authenticating via the updates api (see instance settings in the jomablue portal) authorization bearer \<instance level token> query parameters parameter required description page size no number of results per page maximum and default is 100 only active no when present, filters results to only include events with an active status no value required — include the parameter name to enable only upcoming no when present, filters results to only include events whose finish time has not yet passed no value required — include the parameter name to enable cursor no cursor string from a previous response, used to retrieve the next page of results when a cursor is supplied, all other parameters are ignored — the original request's parameters are preserved in the cursor pagination the endpoint uses cursor based pagination each response includes a cursor value that can be passed in subsequent requests to retrieve the next page when using a cursor, filter and page size parameters from the original request are preserved automatically — any additional parameters supplied alongside the cursor are ignored pagination order is by descending created at time, with id as a tiebreaker for events created at the same time example requests list active, upcoming events (20 per page) curl x get " https //instance jomablue com/integration/api/events?page size=20\&only active\&only upcoming https //instance jomablue com/integration/api/events?page size=20\&only active\&only upcoming " \\ h "accept application/json" \\ h "content type application/json" \\ h "authorization bearer \<token>" fetch the next page using a cursor curl x get " https //instance jomablue com/integration/api/events?cursor=\<cursor string https //instance jomablue com/integration/api/events?cursor=\<cursor string >" \\ h "accept application/json" \\ h "content type application/json" \\ h "authorization bearer \<token>" response format { "results" 1, "data" \[ { "id" "instance name/event/1155", "name" "global tech summit 2026", "start time" "2026 12 01t00 00 00 000000z", "finish time" "2026 12 05t00 00 00 000000z", "description" "annual technology conference and exhibition ", "venue name" "melbourne convention centre", "venue address" "1 convention centre pl, south wharf vic 3006", "timezone" "australia/melbourne", "status" "active", "metadata" { "region" "north america", "tier" "flagship" }, "created at" "2026 06 15t09 30 00 000000z", "updated at" "2026 09 20t14 12 45 000000z", "programs" \[ { "program uid" "6ea0f651 2641 4e3d 9a93 0cd1f704cfb1", "program name" "main conference registration" }, { "program uid" "a1b2c3d4 5678 90ab cdef 1234567890ab", "program name" "vip executive program" } ], "ingest urls" \[ { "uuid" "546cc552 e6bc 4e16 b90e 554513338c13", "type" "eventperson", "name" "crm people ingest", "url" " https //instance name jomablue com/api/webhook/ingest/546cc552 e6bc 4e16 b90e 554513338c13 https //instance name jomablue com/api/webhook/ingest/546cc552 e6bc 4e16 b90e 554513338c13 " }, { "uuid" "7a8b9c0d 1234 5678 abcd ef0123456789", "type" "session", "name" "session ingest", "url" " https //instance name jomablue com/api/webhook/ingest/7a8b9c0d 1234 5678 abcd ef0123456789 https //instance name jomablue com/api/webhook/ingest/7a8b9c0d 1234 5678 abcd ef0123456789 " } ], "updates endpoints" \[ { "uuid" "0d6ec355 776e 4055 8a70 56ef305cadb8", "name" "crm updates integration", "urls" \[ { "type" "lead", "url" " https //instance name jomablue com/updates/api/0d6ec355 776e 4055 8a70 56ef305cadb8/vendor leads https //instance name jomablue com/updates/api/0d6ec355 776e 4055 8a70 56ef305cadb8/vendor leads " }, { "type" "eventperson", "url" " https //instance name jomablue com/updates/api/0d6ec355 776e 4055 8a70 56ef305cadb8/event people https //instance name jomablue com/updates/api/0d6ec355 776e 4055 8a70 56ef305cadb8/event people " }, { "type" "session", "url" " https //instance name jomablue com/updates/api/0d6ec355 776e 4055 8a70 56ef305cadb8/sessions https //instance name jomablue com/updates/api/0d6ec355 776e 4055 8a70 56ef305cadb8/sessions " }, { "type" "sessionparticipation", "url" " https //instance name jomablue com/updates/api/0d6ec355 776e 4055 8a70 56ef305cadb8/session participation https //instance name jomablue com/updates/api/0d6ec355 776e 4055 8a70 56ef305cadb8/session participation " }, { "type" "vendor", "url" " https //instance name jomablue com/updates/api/0d6ec355 776e 4055 8a70 56ef305cadb8/vendors https //instance name jomablue com/updates/api/0d6ec355 776e 4055 8a70 56ef305cadb8/vendors " } ] } ] } ], "cursor" "eyjjcmvhdgvkx2f0ijo ", "page size" 20, "filters" { "only active" true, "only upcoming" true }, "instance" "instance name" } response fields top level field type description results integer number of event records returned in this response data array array of event objects (see below) cursor string opaque cursor string to pass as a query parameter to retrieve the next page null if there are no more results page size integer the page size used for this request filters object shows which filters were applied to this request instance string the jomablue instance name event object field type description id string event identifier in instance/resource/id format (e g my instance/event/1155) name string event name start time string event start time as iso 8601 datetime in utc finish time string event finish time as iso 8601 datetime in utc description string event description text venue name string name of the event venue venue address string full address of the event venue timezone string iana timezone identifier for the event (e g australia/sydney, america/los angeles) status string current event status (e g active) metadata object arbitrary key value metadata associated with the event structure varies per instance configuration created at string iso 8601 datetime (utc) when the event was created updated at string iso 8601 datetime (utc) when the event was last updated programs array list of programs associated with the event (see below) ingest urls array list of ingest endpoints configured for this event (see below) updates endpoints array list of updates api integrations configured for this event, including the urls to poll for each resource type (see below) program object field type description program uid string uuid of the program program name string display name of the program ingest url object field type description uuid string uuid of the ingest endpoint type string the ingest endpoint type (e g eventperson, session, vendor) name string display name of the ingest endpoint url string full url to send ingest payloads to for this endpoint updates endpoints object field type description uuid string uuid of the updates api integration name string display name of the updates api integration urls array list of updates api urls for this integration, one per resource type each item contains a type — the resource type the url serves (lead, eventperson, session, sessionparticipation, vendor) — and a url — the full updates api url to poll for that resource type common integration pattern the event discovery api is typically used as the discovery step in an integration workflow a third party system uses this endpoint to poll /integration/api/events to discover available events and their programs use the ingest urls from the response to know where to send people, session, or vendor data for each event use the updates endpoints urls from the response to poll the updates api for each resource type (e g event people, sessions, vendor leads), to read back data that has been created or modified in jomablue use the ingest api to write back external identifiers (e g crm campaign ids) via organisation uid updates notes all datetime values in the response are in utc (iso 8601 with z suffix) archived events are included by default use only active to exclude them historical events (past finish time) are included by default use only upcoming to exclude them all programs for an event are returned, including those with no people yet — this is by design, as programs (e g campaigns) are often created before attendees are assigned the metadata field structure is configurable per instance and may vary