---
title: Vendors
slug: docs/vendors
createdAt: 2026-04-21T16:34:26.951Z
---

Use a Vendor-type ingest endpoint to create and update vendor (exhibitor/sponsor) records within an event. This enables third-party systems - such as CRMs, sponsorship management platforms, or partner portals - to programmatically manage vendor data in Jomablue.

Typical use cases include:

- Syncing vendor/exhibitor records from a CRM or sponsorship management system
- Creating vendor records ahead of an event from an external partner database
- Updating vendor contact details and display information as they change upstream

### How It Works

Vendor ingest works the same way as People and Session ingest: you send a JSON payload to the ingest endpoint, and Jomablue maps the fields based on the endpoint's configured mapping rules. The endpoint, authentication, rate limits, and request format are identical - the only difference is that the endpoint is configured as a *Vendor* type, and the mapped fields correspond to vendor attributes.

Existing vendors can be matched using a resource\_id (either a formatted identifier as used in the Updates API, or a direct integer record ID). If no match is found, a new vendor record is created.

### Mapped Fields

The following fields are available for mapping within a Vendor ingest endpoint:

| Field                         | Type    | Notes                                                                                                   |
| ----------------------------- | ------- | ------------------------------------------------------------------------------------------------------- |
| resource\_id                  | String  | Formatted identifiers (e.g. acme/vendor/123) generate by Jomablue.  Used for matching existing vendors. |
| organisation\_uid             | String  | An external *unique* identifier for the vendor.                                                         |
| name                          | String  | The vendor's name.                                                                                      |
| display\_name                 | String  | The vendor's public-facing display name (may differ from name).                                         |
| description                   | String  | Vendor description text.                                                                                |
| active                        | Boolean | Whether the vendor is active. Truthy/falsy values are automatically normalised.                         |
| email\_domain                 | String  | The vendor's email domain (e.g. acmecorp.com).                                                          |
| website                       | String  | The vendor's website URL.                                                                               |
| primary\_contact\_first\_name | String  | First name of the vendor's primary contact person.                                                      |
| primary\_contact\_last\_name  | String  | Last name of the vendor's primary contact person.                                                       |
| primary\_contact\_email       | String  | Email address of the vendor's primary contact person.                                                   |

### Example Request

:::BlockQuote
POST /api/webhook/ingest/123e4567-e89b-12d3-a456-426614174000
Authorization: Bearer eyJhbGciOi...
Content-Type: application/json
Accept: application/json
:::



:::BlockQuote
\{
&#x20; "vendor": \{
&#x20;   "resource\_id": "acme/vendor/501",
&#x20;   "organisation\_uid": "EXT-VENDOR-99",
&#x20;   "name": "Acme Corp",
&#x20;   "display\_name": "Acme Corporation",
&#x20;   "description": "Leading provider of cloud infrastructure solutions.",
&#x20;   "active": true,
&#x20;   "email\_domain": "acmecorp.com",
&#x20;   "website": "https\://www\.acmecorp.com",
&#x20;   "primary\_contact\_first\_name": "Jane",
&#x20;   "primary\_contact\_last\_name": "Smith",
&#x20;   "primary\_contact\_email": "jane.smith\@acmecorp.com"
&#x20; }
}
:::

### Considerations

- The same general considerations as People ingest apply: requests are processed asynchronously, a 200 Accepted means queued (not yet processed), and event ordering is not guaranteed.
- Existing vendors are matched by resource\_id. If no match is found, a new vendor is created.
- The resource\_id field accepts both formatted identifiers (e.g. acme/vendor/123 as used in the Updates API) and plain integer record IDs.
