Subscribe to webhooks
Webhook endpoints are configured per tenant in the Stridge Dashboard. The same view doubles as a delivery log — every attempted POST is recorded with its status, headers, and the exact JSON body your server received.
Register an endpoint
In the Stridge Dashboard, open Webhooks → Subscribers and click New subscriber:
The HTTPS URL Stridge will POST to. Use a publicly reachable host with TLS — Stridge does not deliver to http:// URLs.
Subscribe to only the event types your integration handles — see Events list for the catalogue. Anything you don't select is dropped server-side; you won't be charged round-trips for events you don't want.
Stridge generates a per-subscriber signing secret on save. Store it server-side and use it to authenticate every incoming delivery — see Verify signature. The secret is shown once on creation; you can rotate it from the subscriber's settings.
Each subscriber has a Send test action that posts a synthetic event of your chosen type, signed with the real secret. Use it to validate your endpoint end-to-end before pointing real traffic at it.
Keep one subscriber per environment — production, staging, sandbox — each with its own URL and secret. Don't share a secret across environments; if a staging endpoint leaks the secret, production stays safe.
Inspect deliveries
The Webhooks → Deliveries view lists every POST Stridge attempted. Each row is one event delivery (for example uda.settlement.completed). Open a row to see status, event type, timestamp, response code, and the exact JSON body your server received — useful while building handlers or reconciling against settlement records.
What's next
- Verify signature — authenticate every incoming delivery before you trust the body.
- Get missed events — handle deliveries your endpoint dropped or rejected.
- Events list — payload schemas for every event type you can subscribe to.