---
title: Endpoints
slug: docs/MTmi-endpoints
createdAt: 2026-01-22T21:34:34.659Z
---

Updates endpoints are accessed using your &#x7B;&#x7B;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.&#x20;

:::hint{type="info"}
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.&#x20;
- leads - People collected as leads by vendors



### event people&#x20;

`GET updates/api/{updates_endpoint_by_uuid}/event-people`

returns people records for an event.

### sessions&#x20;

`GET updates/api/{updates_endpoint_by_uuid}/sessions`

returns sessions&#x20;

### 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.&#x20;

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.&#x20;

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.&#x20;

:::CodeblockTabs
Typical Response

```json
{
	"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

```json
{
	"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

```json
{
	"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.

:::hint{type="info"}
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.&#x20;
:::



