Configuring
Set the delivery URL, generate a signing secret, toggle delivery, and inspect recent attempts — all from Hub → Developers → Webhooks.
Delivery URL
In Hub → Developers → Webhooks → Configuration, set the URL where Playgent should POST events. Requirements:
- HTTPS (HTTP is rejected).
- Reachable from the public internet.
- Returns
2xxfor successful processing. - Responds within 8 seconds.
You can change the URL at any time. Updates take effect immediately.
Signing secret
The signing secret authenticates that a payload came from Playgent. Generate one in the Configuration tab:
whsec_<64 hex chars>
The secret is shown once. Store it in your secret manager. To rotate, click Rotate secret — Playgent shows the new value, then continues to sign with the new secret.
Rotating the secret invalidates the previous one immediately. If you need a graceful overlap, stage the new secret on your end first, then rotate, then remove the old one.
Enabling and disabling
Toggle delivery without losing your URL or secret. Disabling stops new deliveries but keeps configuration. Useful for incident response or maintenance windows.
Delivery log
The Events tab lists recent deliveries:
| Column | Meaning |
|---|---|
| Timestamp | When the attempt was made (UTC). |
| Event | Event type (e.g. game.completed). |
| Event ID | Stable ID — same value across retries of the same event. |
| Status | delivered, retrying, or failed. |
| HTTP status | Last response code (200, 404, 500, etc.). |
| Latency | Round-trip time, in ms. |
| Attempt | Which attempt (1, 2, 3) was the last. |
Logs are kept for 30 days. Click any row to inspect the request body and response.
Test endpoint
The Configuration tab includes a Send test event button — fires a game.completed payload with synthetic data so you can verify your handler before it sees real traffic.