Skip to main content
Webhooks let Edplay push learner progress to your systems the moment it happens, instead of you polling the API for changes. When a learner finishes a course, Edplay sends an HTTP POST to a URL you control, carrying who did what and when. Common uses:
  • Mark training complete in your HRIS.
  • Issue a certificate as soon as a course is finished.
  • Unlock the next step in an onboarding flow.
  • Stream completion data into your data warehouse.
Each workspace has one webhook endpoint. You configure it in Workspace Settings > Integrations > Webhooks.

​
How a delivery works

1

An event happens

A learner completes a course, or their progress through a course changes.
2

Edplay builds and signs the payload

Edplay serializes the event as JSON and signs it with your workspace signing secret.
3

Edplay sends the request

A POST goes to your endpoint URL, carrying a Signature header and a Timestamp header.
4

Your endpoint responds

Verify the signature, queue the payload, and return a 2xx status within 3 seconds.
5

The attempt is logged

The result appears in the delivery log as Pending, Delivered, or Failed.

​
Before you start

The 3-second limit is the most common cause of failed deliveries. Never do real work inside the request. See Deliveries and retries.

​
Where to go next

Set up your endpoint

Configure the URL, choose your events, and confirm the connection with a test delivery.

Events and payloads

Every event Edplay sends, and the exact shape of each payload.

Verify signatures

Prove a request came from Edplay, with Node.js, PHP, and Python examples.

Deliveries and retries

How to respond, when Edplay retries, and how to read the delivery log.