Esports webhooks.
Push signals and results to your URL.
Webhooks deliver selected events to your endpoint so you are not polling. Register a URL, pick events, and verify delivery signatures per the docs.
Why this surface exists
Polling burns quota and still misses the second a steam fires. Webhooks push the event when it happens.
What the record represents
Webhook rows carry id, url, events[], and status.
Core endpoints
GET/POST /v7/webhooks and DELETE /v7/webhooks/{id}.
| Endpoint | Purpose | Key filters |
|---|---|---|
| GET /v7/webhooks | List webhooks (Quant+) | |
| POST /v7/webhooks | Create webhook | url, events |
| DELETE /v7/webhooks/{id} | Remove webhook |
Canonical IDs
- —webhook id
- —event payloads carry kr_match_id / propId
Sample payload
Example active webhook subscribed to signals and results.
| Field | Example | Used for |
|---|---|---|
| id | wh_… | Webhook id |
| url | https://… | Delivery target |
| events | [signals, results] | Subscribed event types |
| status | active | Delivery state |
GET /v7/webhooks
{
"available": true,
"webhooks": [
{
"id": "wh_example",
"url": "https://example.com/hooks/kashrock",
"events": [
"signals",
"results"
],
"status": "active"
}
]
}Comparing sources
Same signal and results workers — delivered instead of polled.
| Source | Schema | Best use |
|---|---|---|
| Polling every second | Wasteful | DIY |
| Third-party queues | Extra hop | Ops cost |
| KashRock webhooks | Native push | Desks |
How to use it
results events carry the same grades as /results.
Operational practices
- —Verify signatures
- —Keep handlers idempotent
- —Quant for push
Quick reference
POST /v7/webhooks registers a URL for signals and results events. Get your free key.
If you need a normalized feed instead of another UI wrapper, the esports api exposes live boards, schedules, and history on one schema — with the IDs and outcome patterns that keep backtests and grading honest. Start free on Sandbox, or see published pricing.
