ThePerfectMatch Match Webhook Event
The tpm_request.match event is triggered whenever a match is created for a vendor for a ThePerfectMatch request. The event data includes information about the request, and the vendorās response.
The event data is structured as follows:
event: The name of the event, which istpm_request.match.data: An object containing the data for the event.id: The ID of the match.name: The name of the person making the request.email: The email address of the person making the request.telephone: The telephone number of the person making the request.contact_method: The preferred method of contact for the person making the request. This can beno_preference,email,whatsapp, ortelephone.wedding_date: The date of the wedding, in ISO 8601 format.content: The content of the request, describing the type of music and any special wishes.released_at: The date and time when the request was released, in ISO 8601 format.created_at: The date and time when the request was created, in ISO 8601 format.updated_at: The date and time when the request was last updated, in ISO 8601 format.request_information: An object containing additional information about the request.id: The ID of the request information.request_id: The ID of the request.hours: The number of hours requested.budget: The budget for the request.special_wishes: Any special wishes for the request.
response: An object containing information about the response to the request.id: The ID of the response.vendor_reply: The vendorās reply to the request.status: The status of the response. This can beaccepted,rejected, orpending.match_status: The status of the match. This can bematchorno_match.accepted_at: The date and time when the response was accepted, in ISO 8601 format.matched_at: The date and time when the match was made, in ISO 8601 format.created_at: The date and time when the response was created, in ISO 8601 format.updated_at: The date and time when the response was last updated, in ISO 8601 format.
tags: An array of objects containing information about the tags associated with the request. Each object includes the following fields:id: The ID of the tag.name: The name of the tag.
Here is an example of the tpm_request.match event data with fake data:
{
"event": "tpm_request.match",
"data": {
"id": 1234,
"name": "John Smith",
"email": "john@example.com",
"telephone": "+1234567890",
"contact_method": "email",
"wedding_date": "2023-07-01T00:00:00+02:00",
"content": "We are looking for a live band to play at our wedding
reception from 8:00pm to midnight. We prefer a mix of modern and
classic hits. We would also like to have a DJ for the last hour to
play some dance music.",
"released_at": "2022-12-16T14:50:13+01:00",
"created_at": "2022-12-16T14:45:45+01:00",
"updated_at": "2022-12-16T14:50:13+01:00",
"request_information": { "id": 5678,
"request_id": 1234,
"hours": 5,
"budget": 3500,
"special_wishes": "We would like the band to learn and play our first
dance song."
},
"response": {
"id": 9012,
"vendor_reply": "Thank you for considering us for your wedding! We
would love to play at your reception. Our band specializes in a mix
of modern and classic hits, and we can also provide a DJ for the last
hour. Our rate for a 5-hour performance is $3500. Please let us know
if you have any further questions.",
"status": "accepted",
"match_status": "match",
"accepted_at": "2022-12-16T13:50:08+01:00",
"matched_at": "2022-12-16T13:50:08+01:00",
"created_at": "2022-12-16T14:50:08+01:00",
"updated_at": "2022-12-16T14:50:08+01:00" },
"tags": [
{
"id": 1111,
"name": "band"
},
]
}
}