Webhooks
The Webhooks page is where you set the endpoint that receives ryno events, manage the signing secret, and inspect recent deliveries.
Summary
| Item | Description |
|---|---|
| Delivered | Deliveries your endpoint accepted. |
| Pending Review | Deliveries still being retried or awaiting a final result. |
| Failed | Deliveries that did not succeed. |
| Signing header | The header that carries the signature, X-Ryno-Signature. |
Configure your endpoint
Select Configure Webhook
The Endpoint Settings panel opens.
Enter the Webhook URL
It must be a valid HTTP or HTTPS URL.
Set the Webhook Secret
Enter or regenerate the signing secret. New or regenerated secrets become active only after you save.
Test the endpoint (optional)
Select Test Webhook to send a webhook. event to your endpoint.
Select Save Configuration
Changes apply only after you save.
Endpoint requirements
- The endpoint must be publicly accessible.
- HTTPS is strongly recommended.
- ryno sends
POSTrequests. - Respond with a
2xxstatus code to acknowledge the delivery.
Verify the X-Ryno-Signature header on every delivery before trusting it. See Verifying deliveries.
Recent deliveries
Recent Deliveries lists the last 25 delivery attempts. Filter by date range or by status (Delivered, Pending, Failed).
| Column | Description |
|---|---|
| Timestamp | When the event occurred. |
| Event type | For example webhook. or funding_intent.. |
| HTTP status | The status code your endpoint returned on the last attempt. |
| Total attempts | How many times ryno tried to deliver. |
| Status | The delivery status. |
Delivery details
Select View on a delivery to see:
- Delivery ID, Event ID, and Event version
- HTTP status and Total attempts
- Replay and Replay series, if the delivery was replayed
- Occurred at, Next attempt, and Completed at
- Attempt history: for each attempt, when it was sent, the HTTP status, duration, error kind, and your endpoint's response
- Payload JSON: the exact event body that was sent
Use the attempt history to debug an endpoint. For example, repeated 404 responses mean the URL is wrong or the route is not deployed.