Edmingle Webhooks Guide: Automation, Events and Monitoring

A webhook tells your own systems what just happened in Edmingle, the moment it happens. When a learner enrols, completes a course, or submits a test, Edmingle sends a JSON message to a URL you own, so your CRM, ERP, or automation tool can act on it without anyone exporting a report.

This article covers setting one up, the events you can listen for, the shape of the payload, and how to monitor deliveries.

Before you start

Where to find webhooks

Go to Settings → Apps, open the Automation and Webhooks tab, and click Manage on the Webhooks card.

The first time you open it you will see an introduction screen with a Create New Webhook button. After that you get the list of your webhooks.

What your endpoint has to do

Build and test your endpoint before you create the webhook in Edmingle, because you cannot save a webhook until its URL has been validated.

Your endpoint must:

• Be reachable over HTTPS. The form rejects anything that does not start with https://.

• Accept a POST with Content-Type: application/json.

• Respond with 200, 201, or 204.

• Respond with a JSON body, even an empty object like {}. A 200 with an empty or non-JSON body fails validation.

• Respond quickly. Acknowledge first, process afterwards. Do not do slow work before replying.

The validation ping

When you click Validate Webhook, Edmingle posts a test message to your URL that looks like this:

{
  "event": {
    "event_name": "url.validate",
    "livemode": false,
    "event_ts": "2026-10-13T11:42:07+05:30"
  }
}

Create a webhook

1. On the Webhooks list, click New Webhook.

2. Fill in Webhook Basic Details:

3. Click Validate Webhook. You will see Webhook validated or Webhook validation failed. Use View Payload next to the result to see the status code and exactly what your endpoint returned.

4. In the Events section, pick the events you want. They are grouped into categories down the left side. Use View Payload on any event to see a sample of what it sends.

5. Click Create Webhook. You will see "Webhook created successfully!"

The events you can subscribe to

The list you see is grouped by category. These are the events available:

User

Transactions

Course

Assessments

Announcements

Sessions

Some things do not have an event today, including certificate issued, attendance marked, lead or enquiry created, refund processed, and course published.

What a payload looks like

Every event uses the same envelope:

{
  "event": {
    "event": "transaction.user_purchase_completed",
    "livemode": true,
    "event_ts": "2026-10-13T11:42:07+05:30"
  },
  "payload": {
    "user_id": 904113,
    "role": "student",
    "name": "Priya Nair",
    "email": "priya@example.com",
    "contact_number": "9876543210",
    "course_name": "Full Stack Development",
    "bundle_id": 5521,
    "master_batch_id": 88102,
    "master_batch_name": "FSD Nov 2026",
    "original_price": 45000,
    "discount": 5000,
    "final_price": 40000,
    "currency": "₹",
    "enrollment_id": 773210,
    "enrollment_date": 1760000000
  }
}

• event.event identifies the event, in the form category.event, for example user.user_created or course.user_course_completed.

• event.livemode is true for real events.

• event.event_ts is an ISO 8601 timestamp with the server's offset.

• payload is the event-specific body.

[!Important] The envelope does not carry your organization ID or a unique event ID. Identify records using the IDs inside payload, and build your handler to tolerate the same event arriving more than once.

Payload fields vary by event, and the User updated and Announcement Created payloads are large, returning the full profile or announcement object. Always use View Payload on the event itself to see the current structure rather than coding against the sample above.

Security

Because of that, treat the URL itself as a credential:

• Use a long, unguessable path, for example https://api.yourcompany.com/hooks/edmingle/8f3c1a0e9b6d4f27.

• Do not share the URL, put it in a ticket, or commit it to a repository.

• Treat the payload as a notification, not a source of truth. Use the IDs to call back into Edmingle or your own system and confirm before you act on anything financial.

• If your infrastructure allows it, restrict the endpoint by source IP.

Managing your webhooks

The list shows:

Open the actions menu on a row for:

• View Logs

• Edit Webhook

• Mark as Inactive on an active webhook. This takes effect immediately, with no confirmation step.

• Make Active on an inactive one. This opens the edit screen, where you re-validate the URL and save.

Monitoring deliveries

Click View Logs on a webhook to see what has been sent.

The payload drawer is the main debugging tool: it shows your response body next to the request, so a 500 from your service is visible here along with whatever error it printed.

When deliveries fail

A delivery counts as failed when your endpoint returns anything other than 200, 201, or 204.

[!Important] After 5 consecutive failures the webhook is disabled automatically. Edmingle emails your support and admin addresses with the subject "Webhook Subscription disabled". You also get an earlier warning email, "Webhook Subscription failing", before it reaches the limit.

To bring it back:

1. Fix the endpoint.

2. Open the webhook from the list.

3. Click Validate Webhook and confirm it passes.

4. Save.

A disabled webhook will not reactivate until the URL validates successfully, and events that fired while it was down are not replayed.

Troubleshooting