What does not change
- Paths and parameters of the market data, under a new prefix.
- Responses and payloads, on REST and on the WebSocket feed channels.
- Identifiers.
fixtureId,outcomeId,playerId,sportId,tournamentIdare OddsPapi’s, and they are the ones you place orders on. - The WebSocket envelope:
{ channel, type, payload, ts }. - The languages: the same eight, as the first segment of the path. See Languages.
REST
Responses come back unchanged. OddsPapi’s own documentation, at docs.oddspapi.io, stays the reference for every field.
WebSocket
Feed messages carry no
entryId and no broker timestamps. ts is the time Apexium received the message.
Checklist
- Point REST at
https://api.apexiumbet.com/v1/{lang}and send your Apexium key inx-api-key. - Remove calls to the endpoints that are not served.
- Point the WebSocket at
wss://api.apexiumbet.com/v1/wsand log in withreceiveType: "zstd". - Remove the resume logic of the feed channels; reload from
/v1/{lang}onsnapshot_requiredinstead. See Feed channels. - Handle
4003as final, and4004as a limit.