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 order lifecycle
An order can be created, confirmed, settled, cancelled, or rejected. Integrations must preserve state changes rather than treating each order as an immutable record.
Fetch incremental order files
Where a file-based feed is available, first retrieve the file identifiers for the relevant time window, then retrieve each file's order records. Track the last successfully processed window and file identifier.
Use version-aware upserts
The same order may appear in multiple files when its state changes. Compare its version with the version already stored and apply only newer records. Do not assume the newest download contains only new order IDs.
Handle delayed settlement and retries
Settlement may occur after the match ends. Support retries, temporary gaps, and late changes without silently discarding events.
Build reconciliation reports
Compare order counts, stakes, payout amounts, settlement states, and version histories. Alert on missing windows or unexpected changes.
Frequently asked question
Why can one order appear in multiple files?
Because files may be generated from order modification times, a later settlement or update can produce another version of the same order.
Related integration resources
Discuss your integration
For commercial inquiries or to request appropriate technical documentation, contact FB Sports on Telegram.
@Lemon95278