GET https://xquik.com/api/v1/webhooks/{id}/deliveries
Free. This endpoint does not consume credits.
Path parameters
Headers
Operational handoff
Use this endpoint when a system needs to check webhook delivery status. That can be your queue, CRM, warehouse, or alerting system. It returns the 100 most recent delivery records for one webhook, newest first. FollownextCursor for older ones.
Map each delivery to a small incident row before you pass it on. Keep id, streamEventId, status, attempts, receiver status, timestamps, and the chosen action. Do not write the full response to logs.
This endpoint returns delivery attempt metadata only. It does not return the
webhook URL, event type filter, or signing secret. It also does not return raw
payload body, raw signature, or full request headers.
Do not depend on a nextRetryAt field. The response has none. Triage incidents from status, attempts, lastStatusCode, lastError, createdAt, and deliveredAt.Store these fields for support and retry triage.
Delivery ID
Store
id for delivery-level idempotency and support lookup.Event join
Store
streamEventId to join back to the stored monitor event with
GET /events/{id}.Status route
Use
status to route pending, failed, and exhausted deliveries to the
right queue.Attempt count
Use
attempts to see how often Xquik tried a delivery. Retries continue
until your endpoint returns 2xx or 7 days pass.Receiver result
Use
lastStatusCode to separate receiver errors like 500 from unreachable
endpoints with status 0.Failure reason
Show
lastError as the most recent failure reason for the operator.Timing
Compare
createdAt and deliveredAt to measure delivery latency and
recovery time.Incident response handoff
Use one row per delivery when the receiver owner must act. Ignoredelivered rows, wait on pending, and act on failed. An exhausted row
means 7 days passed without a 2xx. Read its event with
GET /api/v1/events/{id}.Repeated failure
Warn after repeated
failed rows. Include attempts, lastStatusCode, and
lastError. That lets the receiver owner separate code errors from
reachability failures.7-day window
Xquik retries every
failed delivery until 7 days pass. No delivery ends
earlier, even after 410 Gone.Event join
Store
streamEventId and link GET /api/v1/events/{id}. That lets support
inspect the monitor event that triggered the delivery.Receiver proof
After fixing the endpoint, send
POST /webhooks/{id}/test. Attach the
signed test result to the incident before waiting for the next event.pending. Return 2xx for a delivery you will never accept. See the retry policy.Fix the receiving endpoint first. Use POST /webhooks/{id}/test to confirm it accepts signed requests. Then call Resume Webhook to start sending waiting and rejected deliveries at once. Without it, a rejected delivery can wait until its 7 days end.Receiver backfill handoff
This endpoint returns 100 delivery rows per page for 1 webhook, newest first. Xquik resends failed deliveries on its own. Use stored event pages only to rebuild work your receiver lost.nextCursor after every event page. Continue
GET /api/v1/events?limit=100&cursor={nextCursor} until hasMore is false.
Then compare each event id with delivery streamEventId values before
replaying your own work. Add monitorId when replaying one account
monitor, or keywordMonitorId when replaying one keyword monitor.Query parameters
Response
200 OK
400 Invalid cursor
{ "error": "invalid_input", "message": "Cursor invalid. Use nextCursor from the previous page, or omit it to start over." }
The cursor is not one this list returned. Send the nextCursor of the previous page, or omit it.401 Unauthenticated
Missing or invalid API key. Check thex-api-key header value.400 Invalid ID
{ "error": "invalid_id" }
The provided webhook ID is not a valid format.404 Not found
No webhook exists with this ID, or it belongs to a different account.429 Rate limited
{ "error": "rate_limit_exceeded", "message": "Too many requests. Try again later.", "retryAfter": 1 }
Too many requests. Wait for the Retry-After header before retrying.Delivery statuses
pending
Xquik has not sent this delivery yet. It may wait while your endpoint is
failing.
delivered
Your endpoint returned
2xx. Delivery is complete.failed
The last attempt failed because the endpoint returned non-
2xx or the
network failed. Xquik retries with exponential backoff until your endpoint
returns 2xx or 7 days pass.exhausted
7 days passed without a
2xx. lastError says why. Read the event with
GET /api/v1/events/{id}.2xx or 7 days pass. Pausing or deleting the webhook holds its deliveries. Each one shows exhausted once its 7 days end. Events expire 30 days after Xquik creates them. An event whose delivery ended as exhausted stays 30 days after that delivery ended.Related. Webhooks Overview · Resume Webhook · Webhook Testing Guide
Response examples
- 400
{ "error": "invalid_input", "message": "Invalid input. Check the request body." } - 401
{ "error": "unauthenticated", "message": "Authentication required. Provide a valid API key or bearer token." } - 403
{ "error": "api_key_paused", "message": "This API key is paused. Resume it at dashboard.xquik.com/api-keys to use it again." } - 404
{ "error": "not_found", "message": "Resource not found." } - 429
{ "error": "rate_limit_exceeded", "message": "Too many requests. Try again later.", "retryAfter": 60 }