This article is an integration planning guide, not a substitute for current authenticated API documentation. Confirm field names, availability, and operational requirements with the integration team.
Understand the integration model
An integration typically connects the merchant's user system to FB Sports services and either an embedded H5/PC experience or a custom frontend. Define your account mapping, currency handling, callback security, and reconciliation process before going live.
Create and map merchant users
Maintain a stable merchant-side user identifier for each account. Validate the supported currency configuration and prevent accidental duplicate mappings within your own system. Treat account creation as a controlled backend operation.
Obtain a user access token
The token service supplies an authenticated user token and service addresses. Use the returned API, H5, PC, and push endpoints rather than assuming every environment shares the same hostname. Keep signing credentials and tokens server-side where appropriate.
Integrate the frontend
Choose the correct H5 or PC entry point. Verify mobile behavior, locale, session expiry, error states, and mixed-content restrictions. Use HTTPS consistently.
Complete end-to-end testing
Test a new user, login, balance, placement, cancellation, settlement, and reconciliation. Confirm retry behavior and error logging in a staging environment before production.
Frequently asked question
What should I test before launch?
Test user mapping, authentication, wallet behavior, bet placement, order updates, and recovery from failed callbacks.
Related integration resources
Discuss your integration
For commercial inquiries or to request appropriate technical documentation, contact FB Sports on Telegram.
@Lemon95278