---
title: "Get webhook delivery logs"
method: GET
path: "/v3/webhooks/{id}/logs"
tags: ["Webhooks"]
---

# Get webhook delivery logs

`GET /v3/webhooks/{id}/logs`

<small>_Requires the `webhooks:read` scope (or a broader one that includes it)._</small>

Returns a paginated **failure log** for a single subscription — only failed
delivery attempts are recorded here; successful deliveries are not listed. Each
log entry captures the triggering event id, HTTP status (or `null` when the
request could not be completed) and the UTC timestamp of the attempt.

## Path parameters

- `id` integer, required

## Query parameters

- `top` integer
- `skip` integer

## Response `200`

Paginated delivery-log entries.

- object
  - `items` object[]
    - `eventId` string, uuid — Unique identifier of the event that triggered the delivery.
    - `httpStatus` integer, nullable — HTTP status code returned by the subscriber endpoint, or `null` if the delivery could not be completed (e.g. network error).
    - `date` string, date-time — ISO-8601 timestamp (UTC) when the delivery attempt was made.
  - `hasMore` boolean — Whether more items are available beyond the current page..

## Other responses

- `400` — Invalid `id` parameter, or invalid pagination parameters.
- `401` — Unauthorized. The response body is empty; check the `WWW-Authenticate` header for the expected scheme.
- `404` — Webhook subscription not found or not owned by the caller.
- `429` — Too Many Requests

---

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