The Contract signed by both parties event notifies your application once a booking's contract has been signed by both the host and the client, so your systems can act on a completed agreement without polling.
Subscribing to the event
Go to Admin Panel.
Click on Webhooks.
Open an existing webhook or click on Add New Webhook.
Select Contract signed by both parties from the list of events.
Click on Save Changes.
New events arrive unselected, so existing webhooks keep their current subscriptions until you select this event.
When the event fires
The event is sent once, at the moment the contract moves to signed by both parties. The order of signing doesn't matter: whether the host signs first or the client does, the event is sent only after the second signature arrives.
A contract signed by just one party doesn't trigger it, and later changes to an already signed contract don't send it again. If the signing provider reports the same completed signature more than once, you still receive a single event.
Payload
The payload is delivered as a POST request and carries the booking details along with a contract object.
id— the booking's identifier.sid— the booking's short identifier.name— the name of the person who booked.email— the email of the person who booked.admin_booking_url— the link to the booking in your admin panel.
The contract object carries:
id— the contract's identifier.title— the title of the signed document.status— the contract status, which issigned_by_bothfor this event.signing_parties— the name and email of each party who signed.sent_at— the time the contract was sent for signing.signed_at— the time the contract became signed by both parties.
See the article Creating webhooks to know more details.