---
title: "Enquiry Webhooks Request"
slug: "webhooks-request"
updated: 2026-06-08T09:31:35Z
published: 2026-06-08T09:31:35Z
canonical: "support.daynurseries.co.uk/webhooks-request"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.daynurseries.co.uk/llms.txt
> Use this file to discover all available pages before exploring further.

# Enquiry Webhooks Request

The webhook request will consist of data in both the HTTP header & body sections.

#### Webhook Headers

The HTTP headers are used for authentication of the message data.

| Name | Purpose |
| --- | --- |
| webhook-id | This is the webhook message id. This can be used to ensure a message is only processed once |
| webhook-timestamp | This is the timestamp that the message was sent. This can used to ensure older messages are ignored. |
| webhook-signature | This is the signature of the webhook message. This can be used to verify that the data has been sent from daynurseries.co.uk |
| webhook-url-id | This is the unique numeric id of the Webhook URL set up in the Portal. The id, for reference, can be found on the Webhooks page within the Portal. |

#### 

#### **Webhook Message**

The message data (HTTP body) is a JSON object representing the event. The event JSON object data has 3 properties; type, timestamp and data. The data property is a JSON object will always have an id property, the other properties will depend on the type of event.

```json
{"type":"brochure.created","timestamp":"2025-04-01T10:26:10.344522Z","data":{"id":"123456"}}
```

#### **Verify the Webhook Signature**

To verify the signature create a text string of 3 parts; webhook-id, webhook-timestamp and the HTTP body(JSON object string), separate the 3 parts with a ’.’, see below for example. Has the string with your secret key & the HMACSHA256 algorithm to match this signature.

```plaintext
msg_2KWPBgLlAfxdpx2AI54pPJ85f4W.1674087231.{"type":"brochure.created","timestamp":"2025-04-01T10:26:10.344522Z","data":{"id":"123456"}}
```