POST request to a URL you control, with the event details in the body.
Available events
A webhook can be triggered by any of the following actions:Webhooks are personal. A webhook only fires for events that concern the member who
created it.
- The
contractCreatedwebhook only triggers if you are a participant of the contract. - The
reminderEventCreatedwebhook only triggers if the reminder is intended for you.
Create a webhook
1
Open the Webhooks settings
Go to My account → Integrations → Webhooks, or open it directly:
Open Webhooks settings
app.tomorro.com → Settings → Integrations → Webhooks
2
Add a webhook
Click Add a webhook.
3
Configure it
- Name your webhook.
- Paste the URL that will receive the events.
- Select one or more triggers (the events that activate it).
- Click Create webhook.
4
Save your signing secret
A secret is generated for the webhook. Tomorro uses it to sign every event so you can
verify authenticity — keep it safe and use it to check the
Leeway-Signature header.Event payloads
Every webhook is delivered as an HTTPPOST with a JSON body. All events share the same
top-level envelope; the event-specific content lives under data.
Envelope
The
data shape depends on eventType. Contract events wrap the contract under
data.contract. Always branch on eventType before reading data.data.contract.initialContractId is the id of the initial contract an amendment belongs to,
or null when the contract is not an amendment. On contractCreated, it is set when the
amendment is created from its initial contract; a contract linked as an amendment after its
creation still reports null in that event.Examples
contractCreated
contractCreated
contractStatusUpdated
contractStatusUpdated
Status-update events include the contract’s lifecycle fields (
status, dateStatus,
realEndDate, …) and the resolved attributes, where each attribute carries a human-readable
valueLabel in addition to its raw value.