Integration
Three pieces of work on your side. Your sportsbook keeps the money, the players and the licence; FAST runs the rules and tells you when to act.
What you build
-
Send bet events
Your backend forwards each placement and settlement to FAST with your server key, one POST per bet. Validate before accepting a challenge bet, or run async so FAST never sits in your bet flow. An adapter reads your existing payload format.
-
Handle webhooks
FAST sends an HMAC-signed webhook on every state change: challenge passed, funded account activated, payout due. Your backend verifies the signature and moves the real money. FAST never touches funds.
-
Embed the widget
One script tag renders the whole player experience. Your backend mints a short-lived token per player with the server key; the browser only ever sees the public key and that token.
-
Approve money actionsOptional
Needed only if players buy, withdraw or cancel from the widget. FAST then calls one approval URL on your backend first, so you collect the stake and apply your own limits before anything is recorded.
Typical time to go live
From staging keys to production. The first API call takes minutes with the Quickstart; most of the time goes into wiring your own payments and settlement, then testing on a staging tenant that you can reset at will.
What you get
TypeScript SDK
@fundedfast/sdk: typed client with retries, idempotent payouts and webhook signature verification. Any other stack uses the same plain JSON over HTTPS.
Staging tenant
Separate keys, sandbox reset, and approvals that auto-approve until you set your URL, so you can run the full flow before production.
Reference and demo
OpenAPI reference with try-it-out, a go-live checklist, and a working demo sportsbook to compare against.
The full guide lives on docs.fundedfast.eu
Every endpoint, payload and edge case, kept in one place and in step with the API.