Endpoints

updates endpoints are accessed using your {{updates endpoint uuid}} you will receive the endpoint uuid after it is created/configured in your event an event may also have multiple endpoints configured, usually for different systems to consume differently mapped datasets none, some or all of these may be configured for an event the response data is dependant on customer needs as jomablue allows for mapping and shaping data as required available resources event people people registered for an event sessions sessions in the event session participation people's attendance of sessions at an event vendors usually referred to as 'exhibitors' 'sponsors' etc leads people collected as leads by vendors event people get updates/api/{updates endpoint by uuid}/event people returns people records for an event sessions get updates/api/{updates endpoint by uuid}/sessions returns sessions session participation updates get updates/api/{updates endpoint by uuid}/session participation returns peoples attendance of sessions within an event vendors updates get updates/api/{updates endpoint by uuid}/vendors returns vendors usually refered to as 'exhibitors' 'sponsors' etc vendor leads updates get updates/api/{updates endpoint by uuid}/vendor leads returns people collected as leads by vendors response data the response data is completly cuustomisable as per customer requirements the response could return one data field (such as an id) or some other combination of data jomablue stores for that resource jomablue has the ability to shape data as well as re map the keys to match customer systems without the need for customer consumers to manipulate data for example, below you can see a typical response for event people along with variations jomablue will work with customers to configure the mapping best suited to them typical response { 	"results" 1, 	"data" \[ 	 { 	 "event id" "acme/event/521", 	 "person organisation uid" "e52a2250 5227 433e 8dcd 27decbf55488", 	 "id" "acme/event person/23151", 	 "first name" "james", 	 "last name" "smith", 	 "company" "a2 consulting", 	 "job title" "solution architect", 	 "email" "j smith\@a2c com", 	 "phone" "+109149441841", 	 "cancelled" false, 	 "checked in" false, 	 "import type" "online free registration", 	 "city" "san francisco", 	 "state" "ca", 	 "country" "us", 	 "zip" "94102", 	 "campaigns" \[], 	 "updated at" "2026 01 12t08 03 01 000000z", 	 "created at" "2026 01 12t08 02 16 000000z" 	 } 	], 	"cursor" null, 	"from" null, 	"to" null } altered keys response { 	"results" 1, 	"data" \[ 	 { 	 "event" "acme/event/521", 	 "contactid" "e52a2250 5227 433e 8dcd 27decbf55488", 	 "jomablue event id" "acme/event person/23151", 	 "first" "james", 	 "last" "smith", 	 "company" "a2 consulting", 	 "primary job title" "solution architect", 	 "business email" "j smith\@a2c com", 	 "mobile" "+109149441841", 	 "cancelled" false, 	 "badge printed" false, 	 "import type" "online free registration", 	 "city" "san francisco", 	 "state" "ca", 	 "country" "us", 	 "zip" "94102", 	 "campaigns" \[], 	 "updated at" "2026 01 12t08 03 01 000000z", 	 "created at" "2026 01 12t08 02 16 000000z" 	 } 	], 	"cursor" null, 	"from" null, 	"to" null } minimal response { 	"results" 1, 	"data" \[ 	 { 	 "event id" "acme/event/521", 	 "person organisation uid" "e52a2250 5227 433e 8dcd 27decbf55488", 	 "id" "acme/event person/23151", 	 "first name" "james", 	 "email" "j smith\@a2c com", 	 "updated at" "2026 01 12t08 03 01 000000z", 	 "created at" "2026 01 12t08 02 16 000000z" 	 } 	], 	"cursor" null, 	"from" null, 	"to" null } api pagination and query parameters the updates api uses cursor based pagination the request can include the following parameters from must be a valid utc iso 8601 datetime (if omitted defaults to a long time ago) to must be a valid utc iso 8601 datetime (if omitted defaults to now) page size must be integer representing the per page (upper limits exist) cursor the cursor returned by the previous request, allows you to get the next page note that the cursor embeds the from and to values used in the initial request and can’t be overridden from and to values supplied in the request params will be ignored if a cursor is included for the most performant responses, we recommend not filtering using from and to the responses you receive will contain the cursor to allow you to iterate over the pages to get all records for the event