---
title: Creating an Endpoint
slug: docs/creating-an-endpoint
createdAt: 2026-09-23T02:21:13.075Z
---

An Ingest API endpoint receives a JSON payload from your own systems, such as a CRM, registration platform, or exhibitor database, and turns it into People, Sessions, or Vendors in your event. Each endpoint has one type and one field map. The field map controls how the endpoint reads your payload and where each value is written. This article walks through creating an endpoint, adding a field map, and posting your first payload.

## Before you start

You need:

- Portal access to the event you want to send data into.
- An Integration Consumer with access to this endpoint, and its long-lived token. See Authentication for how a Consumer exchanges its long-lived token for a short-lived access token.
- The field map for the resource you are ingesting. See [Ingest API Mapping Examples](https://apidocs.jomablue.com/docs/wUWG-mapping-examples) for a worked map for each type.

## Step 1: Open the Ingest API Endpoints tab

Select your event and go to **Advanced > Integrations**, then click the **Ingest Endpoints** tab.

![](https://api.archbee.com/api/optimize/DHKOH0YwbTGPz2KqdQjth/_NeVj7yiIII8rnb7usNIe_cleanshot-2026-09-23-at-122333-2x.png)

## Step 2: Add the endpoint

Click **Add Ingest Endpoint** and give your endpoint a name. The name is for your own reference, so use something that identifies the sending system and the resource, for example "CRM contacts" or "Registration sessions".

Choose the type the endpoint accepts:

- **EventPerson** creates and updates People.
- **Session** creates and updates agenda Sessions.
- **Vendor** creates and updates Vendors.

An endpoint has one type. To ingest more than one resource, create one endpoint per resource.

![](https://api.archbee.com/api/optimize/DHKOH0YwbTGPz2KqdQjth/WDciqQPFhbPIo-VAFv7FM_cleanshot-2026-09-23-at-122426-2x.png)

## Step 3: Add the field map

Click on **Advanced (JSON)** and then paste your field map into the endpoint. The field map is a list of rules. Each rule reads a value from your payload (keyMatch) and writes it to a Jomablue field (type).&#x20;

Point each keyMatch at wherever the value lives in your payload, using dot notation (for example contact.email). Anything in the payload that no rule references is ignored. For the full map for each type, the available fields, and how records are matched, see [Ingest API Mapping Examples](https://apidocs.jomablue.com/docs/wUWG-mapping-examples).

![](https://api.archbee.com/api/optimize/DHKOH0YwbTGPz2KqdQjth/nTgHlkv1MAU0Ki-VJWfQW_cleanshot-2026-09-23-at-122623-2x.png)

## Step 4: Add validation rules (optional)

You can attach validation rules that check a payload before it is mapped. Each rule targets a payload key and applies one or more checks separated by `|`. You choose whether a payload that fails is rejected with an error or skipped quietly, before anything is created or updated. Each mapping article includes an example rule set you can adapt.

![](https://api.archbee.com/api/optimize/DHKOH0YwbTGPz2KqdQjth/feFXPc0kfxoAT-E7esLR2_cleanshot-2026-09-23-at-122757-2x.png)

## Step 5: Copy the endpoint URL

Save the endpoint, then copy its **URL**. This is the URL your system posts payloads to. Send your short-lived access token as the Bearer token on each request.

![](https://api.archbee.com/api/optimize/DHKOH0YwbTGPz2KqdQjth/N-qOdKpgNXSf62-nAp9Ys_cleanshot-2026-09-23-at-122826-2x.png)

## Verify

Confirm the endpoint works end to end:

1. Exchange the Consumer's long-lived token for a short-lived access token (see Authentication).
2. Post a sample payload to the URL you copied, sending the short-lived token as the Bearer token:

:::BlockQuote
curl --request POST \\
&#x20; \--url https\://your-instance.jomablue.com/api/webhook/ingest/&#x7B;endpoint-uuid} \\
&#x20; \--header 'Authorization: Bearer \<short-lived-token>' \\
&#x20; \--header 'User-Agent: your-system-name' \\
&#x20; \--header 'Accept: application/json' \\
&#x20; \--header 'Content-Type: application/json' \\
&#x20; \--data '\{ "organisation\_uid": "CRM-10432", "first\_name": "Jane", "last\_name": "Doe", "email": "jane.doe\@example.com" }'
:::

A successful response confirms the payload was accepted and mapped. Send the same organisation\_uid again with new values and the record is updated in place rather than duplicated. For a worked payload and result for each type, see Ingest API Mapping Examples.
