Skip to content
English
  • There are no suggestions because the search field is empty.

Test deliveries vs live deliveries

Technical details of how Empath's two Test webhook buttons differ from live deliveries, and how to recognise test payloads.

Technical details of Empath's test requests, so your receiver can handle them and you can read the results correctly.

How do tests differ?

  • Signed with — Wizard test (Review & test): a temporary secret · Row test (saved webhook): your real secret
  • Event type sent — Wizard test (Review & test): the first event you ticked · Row test (saved webhook): the first event saved on the webhook
  • tenantId — Wizard test (Review & test): test-tenant · Row test (saved webhook): your real company ID
  • Result shown — Wizard test (Review & test): Data sent / Data received · Row test (saved webhook): Test delivered (…) or Test failed

Test payloads use placeholder data:

{
  "id": "evt_test_<…>",
  "type": "course.assigned",
  "createdAt": "
  
   ", "tenantId": "
   
    ", "data": { "user": { "id": "test-user", "email": "test@example.com", "displayName": "Test User" }, "object": { "type": "course", "id": "test-object", "title": "Test Object" } } } 
   
  

Good to know

  • Test IDs always start with evt_test_. Ignore or tag them in production logic.
  • A successful test doesn't prove live events will arrive. Tests skip the training system. To prove the live path, assign a real course to a real person and confirm a course.assigned whose id starts with whk_.
  • Tests don't count towards the Delivered and Failed numbers.

Still need help?

Reach out to your Partner Success Manager, or email us at support@empathmsp.com. We’re happy to help!

Related articles

  • Create a webhook: Review & test and the signing secret
  • Edit, test or delete a webhook
  • Troubleshooting webhooks