---
title: "Get a webhook"
method: GET
path: "/webhooks/{webhookId}"
tags: ["webhook"]
---

# Get a webhook

`GET /webhooks/{webhookId}`

Retrieves a single webhook subscription: its target URL and the events currently delivered to it. Use `GET /webhooks` to discover the identifiers of your webhooks.

**Permission:** No specific permission required. A valid API key is sufficient.

**Monitoring:** Not needed.

## Path parameters

- `webhookId` string, uuid, required

## Response `200`

Successful operation — returns the webhook details.

- WebhookSubscription
  - `uuid` string, uuid, required — The identifier of the webhook: an RFC 4122 v5 UUID derived from `target_url` in the URL namespace. The same target URL always yields the same identifier, and it is stable for the lifetime of the subscription.
  - `target_url` string, uri, required — The URL Ringover POSTs the subscribed events to. Immutable.
  - `events` WebhookEvent[], required — The events delivered to `target_url`, in catalog order.
  - `signing_key` string — The key used to sign the deliveries sent to your endpoints (see *Securing your webhooks* in the `webhook` tag description). Read-only and shared by every subscription of your configuration. Absent while no key has been generated yet.

## Other responses

- `401` — Authentication token is missing, invalid, or expired
- `403` — The API key is not allowed to manage webhooks
- `404` — No webhook matches this identifier
- `500` — Internal server error

---

[API](https://skmtc.net/ringover/apis/ringover-public-api.md) · [All operations](https://skmtc.net/ringover/apis/ringover-public-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/ringover/ringover-public-api/revisions/9da73dd2f99e/schema)