Vendor Mapping
A Vendor ingest creates or updates a Vendor (exhibitor, sponsor, or partner) in an event from a JSON payload — usually a webhook from your CRM or exhibitor system. It's a small, flat mapping: copy it, point the paths at your own payload, and you're done.
How it works
A field map is a list of rules. Each rule reads a value from your payload (keyMatch) and writes it to a Jomablue Vendor field (type). Point each keyMatch at wherever the value lives in your own payload, using dot notation (e.g. vendor.primaryContact.email).
Vendors are matched by resource_id first, then by organisation_uid. If neither matches an existing Vendor, a new one is created. New Vendors must have a name. Anything in the payload that no rule references is ignored.
The mapping
The fields
resource_id — the Vendor's internal ID, and the primary way Vendors are matched. Accepts a plain integer or a formatted string like app_name/vendor/123 (the trailing number is used).
organisation_uid — your own identifier for the vendor. Used for matching when there's no resource_id, and stored on the Vendor either way.
name — the Vendor name. Required to create a new vendor.
display_name — the name shown publicly. Defaults to name for new Vendors if you don't provide it.
description — a description of the vendor.
active — whether the Vendor is active. Accepts true, 1, "yes", "true", "1" (case-insensitive); anything else is false. New Vendors default to active if you don't map this.
email_domain — the Vendor's email domain (e.g. northwindlabs.com).
website — the Vendor's website URL.
primary_contact_first_name / primary_contact_last_name / primary_contact_email — the Vendor's main point of contact. In the example these read from a nested primary_contact object in the payload.
Worked example
Payload:
Result: Vendor 58 (matched by resource_id, else created) named "Northwind Labs", shown as "Northwind", active, with the given description, email domain, and website, and a primary contact of Sam Okafor. Send the same resource_id again with new values and the Vendor is updated in place.
Validation
You can validate the payload before it's mapped. Each rule targets a payload key and applies one or more checks separated by |; a payload that fails is rejected before anything is created.
- required_without — at least one identifier is needed. resource_id is required only when organisation_uid is absent, and vice versa.
- required — name must be present to create a vendor.
- nullable — checked only when present: the contact name fields must be strings, and the contact email must be a valid email.
Match these keys to your own payload paths.