Webhooks

Overview

Server-side delivery of game events. Configure an endpoint, verify signatures, and trust that even on transient failures the event will retry.

Webhooks are how Playgent tells your servers about events that happen client-side — completions, in particular — with cryptographic verification and retries. If you need:

• An auditable record of completions (warehouse, analytics).
• Server-side gating of rewards or premium content.
• Detection signals for fraud or abuse.

…webhooks are the right tool. Don't trust client-side onComplete for any of those.

What you get

• A signed POST to a URL you control.
• HMAC-SHA256 signatures with a 5-minute replay window.
• Three delivery attempts with exponential backoff.
• A 30-day delivery log in the Hub.

What you provide

• A public HTTPS endpoint that returns 2xx quickly (under 8 seconds).
• A secret you store securely and use to verify signatures.

Events

Event	When
game.completed	A user finished a game. Includes score, duration, identity, and game/content references.

More events ship over time. New event types are additive — your existing handlers won't break.

Next

1. Configure an endpoint — URL, secret, enabled toggle.
2. Verify signatures — example handlers in Node, Python, Go.
3. Understand retries — when we retry, how long, how to be idempotent.
4. game.completed reference — full payload schema.