Migrating from OddsPapi requires an explicit crosswalk for fixtures, markets and outcomes. Keep the original identifiers and test failure handling before changing the feed your application reads.
This is a preparation guide. It does not claim that Oddswire offers equivalent coverage or that customer source-data access is already approved.
Inventory before translating
Record the API version, endpoint, filters, native identifiers, price format, timestamps and quota behavior your integration currently uses. The OddsPapi V4 documentation describes fixtures, markets, odds and streaming. Its B2B documentation is separately versioned: confirm the contract used by your actual account.
| Concern | Preserve from the old integration | Review in Oddswire |
|---|---|---|
| Fixture | Original fixture and participant IDs | Approved correspondence, kickoff and orientation |
| Market | Native market/outcome IDs and period | Market family, outcome, line and settlement identity |
| Price | Original value, state and time | Native unit, observation timestamp and explicit missing reasons |
| Access | Existing provider permissions | Account, product and source-use scope |
| Recovery | Last accepted complete state | Suspension, resnapshot, pagination and uncertain delivery behavior |
A safe cutover sequence
- Export your configuration without credentials. Write down each assumption your application makes about missing or suspended offers.
- Discover candidate events in the approved target namespace. Review participants, competition and kickoff. Do not merge permanent provider IDs just because names look similar.
- Confirm complete outcomes under matching period, settlement, fees and currency. Fixture correspondence alone does not approve a price comparison.
- Transform one retained, permitted sample. Preserve decimal strings, native IDs and original timestamps alongside normalized fields.
- Test stale data, removed outcomes, authorization withdrawal, rate limits, pagination conflicts and timeouts. Do not automatically retry an uncertain metered delivery.
- Keep the prior integration available for a routing rollback during a separately approved shadow test. A rollback must not rewind usage or rewrite retained evidence.
The contract comparison, settlement guide, and historical data documentation explain the main boundaries. Read access requirements before arranging a live cutover.
Questions
Can I reuse the same fixture IDs?
Keep them as source-native identifiers. A reviewed crosswalk can link observations without making two providers' permanent IDs interchangeable.
Can I map markets by display name?
A name is insufficient. Review period, line, outcomes, settlement and fees before approving compatibility.
Does matching a fixture approve its odds?
No. Event identity and market compatibility are separate decisions.
Should timeouts be retried automatically?
An uncertain response may already have been delivered or charged. Follow the target API's documented recovery behavior instead of assuming retries are free.
Does this guide grant Oddswire source access?
No. Product signup, migration preparation and source-use permission remain separate.