Developer Tools
Outgoing webhooks
Signed HTTPS notifications to your own systems whenever something happens at your body.
Outgoing webhooks
- Availability
- Available
- Category
- Developer Tools
- How it connects
- Built into Qualeron
- Built by
- Qualeron
- Plans
- Included in Professional, Scale and Enterprise.
What it does
Outgoing webhooks, in Qualeron
Qualeron sends a signed POST to an address you control for each event you subscribe to: registrations confirmed, results released, credentials issued, renewed or revoked, vouchers redeemed, and the steps of an application.
Every delivery carries a timestamped HMAC-SHA256 signature. A failed delivery is retried on a schedule and can be replayed, and an endpoint that keeps failing is paused rather than ignored.
Any service or automation tool that accepts HTTPS webhooks can receive them.
- Up to ten endpoints, each with its own events
- Signing secret shown once, stored encrypted, rotated on demand
- Retries, replay, a delivery log, and a test event
Your data
What it reads, what it sends, and what it never touches
It reads
Nothing.
It sends or writes
- The event, the program and the record's reference
- The candidate's name, and their email address on registration and credential events
- The outcome and scaled score when a result is released
It never touches
- Exam answers or uploaded files
- Payment card details
Setting it up
How it is set up
- Open Developer tools in Integrations.
- Add an HTTPS endpoint and choose its events.
- Copy the signing secret into your receiver and send a test event.
Plans
What the plans say
Included in Professional, Scale and Enterprise.
| Plan | Outgoing webhooks |
|---|---|
| Launch | Not included |
| Professional | Included |
| Scale | Included |
| Enterprise | Included |
More in Developer Tools
Next step
Use Outgoing webhooks with Qualeron
Certifying bodies on Qualeron connect it under Settings, then Integrations. New to Qualeron? A specialist will walk you through the plans.