Continue with the OddsPapi migration checklist.
Plan the migration as a reviewed crosswalk between provider contracts. Start only after the target account and source-use permissions cover your application.
- Inventory sport and event IDs, bookmaker regions, market periods, line units, outcome orientation, timestamps, and usage assumptions.
- Discover prospective Oddswire fixtures in the intended namespace. Review participants, kickoff, competition, and orientation. Retain both providers' IDs.
- Review each market's outcomes and settlement rules. A three-way regulation h2h can be considered for a 1X2 crosswalk. A two-way offer requires a separate decision.
- Use the Oddswire key in X-API-Key. Keep decimal values as strings and retain data, missing reasons, and response metadata together.
- Exercise partial results, stale observations, suspension, pagination conflicts, revoked access, and timeouts. A timeout can leave delivery and charging uncertain.
- Compare permitted observations in a controlled shadow test before cutover. Preserve a rollback path to the prior integration.
Oddswire customer data access and source-use rights require review. This checklist describes preparation for approved access.
Read the contract comparison, data conventions, credit rules, and settlement guide.