- From the Openlayer dashboard, under your workspace settings.
- Programmatically, through the REST API.
Only workspace admins can create and manage webhooks, see Roles and
permissions for more details.
Manage webhooks in the dashboard
The webhooks settings page is where most users create and monitor their subscriptions.Open your workspace settings
Click the workspace name in the upper-left corner, select Workspace
Settings, then open the Webhooks section.
Add a webhook
On the Webhooks tab, create a new subscription and fill in the form:
- URL — the HTTPS endpoint that will receive events.
- Event types — one or more event types to subscribe to.
- Description — an optional label to help you identify the subscription.
Copy the signing secret
After you create the subscription, Openlayer shows the signing secret
once. Copy it and store it securely — you’ll use it to verify
signatures, and it can’t be retrieved
later.
View deliveries
Switch to the Deliveries tab to see recent delivery attempts. Each attempt shows whether it succeeded, failed, or is still pending, along with the HTTP status code and response time. Select a delivery to inspect its details, including the response body or error message — useful for debugging an endpoint that isn’t receiving events as expected.Delivery records are retained for 90 days. For how deliveries and retries
work, see the Webhooks overview.
Manage webhooks with the REST API
If you’d rather manage subscriptions programmatically — for example, to provision them as part of your infrastructure — use the REST API.Before you begin
All requests are authenticated with an API key passed as a bearer token, and are made against the base URLhttps://api.openlayer.com/v1:
{workspaceId}, the UUID of your workspace,
which you can find in your workspace settings.
Create a webhook subscription
Send aPOST request with the endpoint url and the eventTypes you want to
subscribe to.
| Field | Type | Required | Description |
|---|---|---|---|
url | string | Yes | The HTTPS endpoint to deliver events to (max 2048 characters). |
eventTypes | string[] | Yes | One or more event types to subscribe to. |
description | string | No | An optional human-readable description (max 500 characters). |
enabled | boolean | No | Whether the subscription is active. Defaults to true. |
id and its signing secret:
List webhook subscriptions
page and perPage query parameters. Note
that the signing secret is never included when listing or retrieving
subscriptions.
Retrieve a webhook subscription
404 Not Found if the
subscription does not exist.
Update a webhook subscription
Send aPUT request with the fields you want to change. You can update the
url, description, eventTypes, and enabled status.
enabled to false lets you pause deliveries without deleting the
subscription. The response returns the updated subscription object.
Delete a webhook subscription
204 No Content.
List delivery attempts
To debug deliveries, list the recent attempts for a subscription. Each record describes one attempt, including the HTTP status code and response time.| Field | Description |
|---|---|
attemptNumber | Which attempt this record represents (1 is the initial attempt). |
success | Whether the attempt received a 2xx response. |
statusCode | The HTTP status code returned, or null if the connection failed. |
responseBody | The first 1 KB of the response body, for debugging. |
responseTimeMs | How long the attempt took, in milliseconds. |
errorMessage | The error, if the attempt failed. |
page and perPage query parameters.
Delivery records are retained for 90 days. For more on how deliveries and retries
work, see the Webhooks overview.
