Skip to main content

Webhook Details in RecordsKeeper.AI - Monitor, Secure, and Troubleshoot Deliveries

This article explains the Webhook Details view - where to find it, how to read the overview charts and delivery logs, and how to manage secrets and authentication for a reliable, secure integration.

Kanishka Sharma avatar
Written by Kanishka Sharma
Updated this week

Introduction

Once a webhook is live, you’ll want quick answers: Is it receiving events? How fast? Why did something fail? Webhook Details brings all of that together - charts for trend-watching, a delivery feed for recent activity, and a side panel with security, versions, and endpoint info.


Getting here

Go to Widgets & Integration → API & Webhook Integration → Webhooks, then click the webhook name. You’ll land on Webhook Details with two tabs: Overview and Event Deliveries.

Overview: the health snapshot

At the top you’ll see the Webhook Event Destination (URL + status) and an Edit Webhook button for quick updates.
Two charts help you spot patterns:

  • Event Deliveries shows successful vs. failed sends over time.

  • Event response time tracks min/avg/max latency to your endpoint.

On the right, Destination Details summarize everything important—Destination ID, Endpoint URL, Description, API Version in use, and how many events this webhook listens to. You’ll also find the Signing Secret (for verifying payload signatures) and Basic Authentication controls to manage username/password on the endpoint.

Event Deliveries: investigate any event

The feed lists each event (e.g., file.upload.success) with its status and timestamp. Select a row to open the inspector on the right. You’ll see:

  • Core context: Status, Event ID, Origin/Source, IP, API Version.

  • Attempts with latency, failure reason (e.g., endpoint unreachable, 4xx/5xx), and retry timing.

  • Expandable Request body and Response body to confirm exactly what was sent and how your server replied.

From here you can refresh the feed, search for a specific event, or jump back to Edit Webhook to update the URL, events, auth, or version.


Pointers

  • Verify signatures using the Signing Secret before processing payloads.

  • Keep handlers light: return a 2xx quickly and do heavy work async to avoid retries.

  • Use Basic Auth and rotate credentials/secret periodically.

  • Separate webhooks by environment or workflow so changes don’t collide.


Conclusion

Use Overview to keep an eye on trends and configuration, and Event Deliveries to drill into the exact request, attempt, and payload. With both views, you can spot problems fast, make precise fixes, and keep your webhook integration reliable and secure.

Did this answer your question?