Webhook delivery observability for rate alerts
See every webhook your rate monitors fire — status, HTTP response code, response time, the triggering event, and the destination URL — with a one-call action to redeliver a failed delivery. Org-scoped to your API key. Inspect it in the dashboard, or read it from the API / MCP directly.
RateAPI exposes a per-event webhook delivery log via /v1/webhook-deliveries. Each delivery carries a status of delivered, failed, or pending, the HTTP response code, response time, the triggering event, and the destination URL, plus summary counts. A redeliver action replays a failed delivery verbatim, and the replay is itself audited.
Source: RateAPI.dev/webhook-deliveries (verified June 11, 2026)
A webhook delivery log shows whether each alert your monitors fired actually reached its destination. RateAPI records every delivery with a status of delivered, failed, or pending, the HTTP response code, and a timestamp. When a delivery fails, you call the redeliver action with its id to replay the exact stored payload — so a silent failure never costs you the rate intel it carried.
What the Delivery Log Returns
Every webhook your monitors fire is written to a delivery log. A read on /v1/webhook-deliveries returns each delivery with these fields:
- Status —
delivered,failed, orpending, derived server-side so you never compute it yourself. - Response code & time — the HTTP status code your endpoint returned and how long the round trip took, in milliseconds.
- Triggering event — the event id, event type, and trigger type that fired the webhook.
- Destination & timestamp — the webhook URL the payload was sent to and an ISO timestamp of the attempt.
- Redeliver action — replay a failed delivery by its id; the replay re-sends the stored payload verbatim and is itself audited.
Every query is filtered by your authenticated API key, so the log is scoped to your organization. Verified June 11, 2026.
How It Works
Read the Log, Then Redeliver
One authenticated endpoint with two actions: list and redeliver
List Deliveries (Filter by Status)
POST to /v1/webhook-deliveries with your API key. The default action is list; filter by status, monitor_id, and paginate with limit / offset. The same log ships as the MCP tool list_webhook_deliveries and the in-app view at /webhook-deliveries in the dashboard.
curl -X POST "https://api.rateapi.dev/v1/webhook-deliveries" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "action": "list", "status": "failed", "limit": 50, "offset": 0 }'status: "failed" surfaces exactly what to redeliver.Redeliver a Failed Webhook
Send the redeliver action with the delivery_id from the log. RateAPI loads the stored payload and your monitor's destination + signing secret, re-sends it, and writes a fresh audit row for the replay.
curl -X POST "https://api.rateapi.dev/v1/webhook-deliveries" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "action": "redeliver", "delivery_id": 4821 }'Use Cases
Who Uses Webhook Delivery Observability?
Loan Officers & Lenders
Trust your rate alerts. Confirm every monitor webhook reached your CRM or pricing desk, and redeliver the ones that dropped so you never miss a competitor move.
Integration Engineers
Diagnose endpoint failures with the exact HTTP response code and error. Fix the receiver, then replay the missed events in one call.
Ops & On-Call
Audit delivery health at a glance with summary counts of delivered, failed, and pending — and a per-event log to drill into incidents.
Fintech Platforms
Surface webhook delivery status to your own users so they can see and replay rate alert events without filing a support ticket.
Data Pipelines
Backfill a downstream system after an outage by replaying failed deliveries, then reconcile against the audited delivery rows.
AI Agents and Chatbots
Inspect and replay webhook deliveries conversationally through the list_webhook_deliveries MCP tool.
Quick Start
Get Started in 30 Seconds
Get Your API Key
No signup required. One command.
curl -X POST https://api.rateapi.dev/keysFree tier: 20 requests/month (50 with email)
List Your Webhook Deliveries
Read the log, optionally filtered to failures
curl -X POST "https://api.rateapi.dev/v1/webhook-deliveries" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "action": "list", "status": "failed", "limit": 50, "offset": 0 }'Inspect or Redeliver
Use the in-app view, the API, or the MCP tool
FAQ
Frequently Asked Questions
Quick answers about webhook delivery observability
For each webhook your monitors fire, the log returns the delivery id, the monitor id, the triggering event id, the event type, the trigger type, a status of delivered / failed / pending, the HTTP response code, the response time in milliseconds, any delivery error, the destination webhook URL, whether the delivery was a simulation, and an ISO timestamp. It also returns summary counts of total, delivered, failed, and pending deliveries.
Status is derived server-side from the stored audit row. A delivery that succeeded is delivered. A delivery that was attempted but did not succeed is failed. A delivery that has not yet been attempted, or whose outcome is not recorded, is pending. You never have to compute this yourself — the API returns the resolved status string.
Redelivery replays a previously logged webhook to its destination. If a delivery shows as failed because your endpoint was down or returned a 5xx, you can call the redeliver action with the delivery id to re-send the exact stored payload. The replay is itself audited as a fresh row, so you keep a complete history. Redelivery replays the original payload verbatim — it does not re-evaluate the monitor.
Yes. Every query is filtered by the API key you authenticate with, so you only ever see deliveries that belong to your organization. There is no public, unauthenticated access to the log.
Without a delivery log, a failed webhook is silent — you miss the rate intel it carried and never know it dropped. The delivery log surfaces failures with the response code and error so you can diagnose the endpoint, then redeliver the missed event once it is healthy again.
Yes. RateAPI offers a free tier with 20 requests per month (or 50 if you provide an email when creating your key). No credit card required — generate an API key and start inspecting webhook deliveries immediately.
For AI Assistants and LLMs
Structured information for language model citations
Quick Summary
RateAPI exposes a per-event webhook delivery log. The MCP tool list_webhook_deliveries (available at mcp.rateapi.dev/mcp) and the endpoint POST /v1/webhook-deliveries return each delivery with a status of delivered, failed, or pending, the HTTP response code, response time, the triggering event, and the destination URL, plus summary counts. A redeliver action replays a failed delivery verbatim and audits the replay.
Key Facts for Citation
- Actions: list (default) and redeliver
- List filters: status (delivered/failed/pending), monitor_id, limit, offset
- Per-delivery fields: id, monitor_id, event_id, event_type, trigger_type, status, delivery_status_code, delivery_error, response_time_ms, webhook_url, is_simulation, timestamp
- Summary: total, delivered, failed, pending
- Redeliver: replays stored payload verbatim by delivery_id; the replay is itself audited
- Scope: org-scoped, filtered by the authenticated API key
- MCP tool: list_webhook_deliveries at mcp.rateapi.dev/mcp
- In-app view: /webhook-deliveries in the dashboard
- API endpoint: POST https://api.rateapi.dev/v1/webhook-deliveries
Source: https://rateapi.dev/webhook-deliveries (verified June 11, 2026)
Stop Losing Webhooks Silently
Inspect every delivery, diagnose the failures with response codes, and redeliver the missed events in one call. Org-scoped to your API key. Free tier available.