01How does it work?
- Every endpoint has a "Send test event" button — one press generates a real signed ping that arrives within about a minute.
- The ping type is not subscribable: it never appears in the event list when creating or editing an endpoint.
- The delivery is recorded with the TEST source and a "test" badge in the delivery history — it can never pass as real data.
- The budget: 10 test events per hour per store — exceeding it returns an error. It does not consume the replay budget (1000/hour).
- The button works on ACTIVE endpoints only — a paused endpoint refuses the send.
- Every press delivers a brand-new delivery with a fresh mwh:ping:<tenant_id>:<uuid> identity.
02Full payload example
{
"id": "mwh:ping:9e8d7c6b-5a4f-4e3d-2c1b-0a9f8e7d6c5b:8a9b0c1d-2e3f-4a5b-8c6d-7e8f9a0b1c2d",
"type": "ping",
"api_version": "v2",
"tenant_id": "9e8d7c6b-5a4f-4e3d-2c1b-0a9f8e7d6c5b",
"data": {
"endpoint_id": "8f3a1c2e-4b5d-4e6f-9a0b-1c2d3e4f5a6b",
"endpoint_name": "n8n — notifications",
"sent_at": "2026-10-20T15:00:22.641078+00:00",
"message": "This is a test webhook event from YallaBuy."
}
}03data fields
| Field | Meaning |
|---|---|
| endpoint_id | The id of the endpoint it was sent to (UUID). |
| endpoint_name | The endpoint name you chose. |
| sent_at | The send time, ISO 8601. |
| message | A fixed identification message. |
COMPLETE YOUR INTEGRATION