Skip to main content
Open Settings → Integrations → Webhooks when the API feature is active. A webhook sends an event to your tool’s URL; an API key lets that tool query EatNow. The two uses complement each other. The technical webhook reference centralizes payloads, signatures, examples and delivery limits. Events do not cover every workflow: review coverage with your developer. The interface offers up to three configurations per restaurant.

​
Create the connection

  1. Prepare a receiving URL with your developer.
  2. Click Create webhook, enter a name and the URL.
  3. Choose events: Reservation created, updated or deleted.
  4. Set a timeout between 1,000 and 30,000 ms, plus custom headers if required by the receiver.
  5. Save and configure the signing secret on the receiver.
  6. Check that the webhook is active.
Cancellation changes a reservation; it does not necessarily delete it. Do not track cancellations solely through the “deleted” event.

​
Test and check signatures

Test sends a real request to the receiver. Coordinate it with the receiver’s owner, then check event receipt and processing. Your developer must implement signature verification. Do not override EatNow’s technical headers with custom headers. Regenerate secret requires updating the receiver, or it will reject new messages. A successful test response checks connectivity, not every business rule in the external system.

​
Stop or diagnose delivery

Deactivate the webhook to pause sending, or delete it when no longer used. If nothing arrives, check activation, selected events, URL, server response and timeout. Give support the restaurant, webhook name, time and expected event. Do not include the secret or authentication headers.