Vendor Lead
The Vendor Leads endpoint sends a Lead captured by a Vendor, linking a Person to a Vendor. Its endpoint is served at /updates/api/{endpoint-uuid}/vendor-leads.
How it works
The template is the shape of the payload you want out. Each key is yours to name; the merge tag on the right supplies the value at send time. One key carries a JSON value rather than text, so its tag sits without quotes: tags. Everything else is plain text and stays quoted.
This record links a Person to a Vendor. The Vendor is identified by vendor_id and vendor_organisation_uid; the Person by event_person_id and person_organisation_uid.
Sample mapping
Sample output
One rendered Lead from the array the endpoint returns:
Field reference
Key | Merge tag | Emits |
|---|---|---|
resource_id | <<RESOURCE_ID>> | Text. The Lead's resource ID. |
vendor_id | <<VENDOR_ID>> | Text. The linked Vendor's resource ID. |
vendor_organisation_uid | <<VENDOR_ORGANISATION_UID>> | Text. Your own identifier for the Vendor. |
event_person_id | <<EVENT_PERSON_ID>> | Text. The linked Person's resource ID. |
person_organisation_uid | <<PERSON_ORGANISATION_UID>> | Text. Your own identifier for the Person. |
notes | <<NOTES>> | Text. Free-text notes captured against the Lead. |
tags | <<TAGS_LIST|format:json>> | JSON array of the Lead's Tags. Unquoted in the template. |
updated_at | <<UPDATED_AT>> | Text. ISO 8601 timestamp. |
created_at | <<CREATED_AT>> | Text. ISO 8601 timestamp. |