Skip to main content
The market data of the Apexium API is OddsPapi v5. A client written for OddsPapi keeps its models and its parsing. What changes is how it connects, and which parts it can reach.

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, tournamentId are 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

Close code 4003 changes meaning. At OddsPapi, it means too many connections. At Apexium, it means that the key or the account is no longer active, and you must not reconnect with it. The connection limit is 4004 at Apexium. See Close codes.
Feed messages carry no entryId and no broker timestamps. ts is the time Apexium received the message.

Checklist

  1. Point REST at https://api.apexiumbet.com/v1/{lang} and send your Apexium key in x-api-key.
  2. Remove calls to the endpoints that are not served.
  3. Point the WebSocket at wss://api.apexiumbet.com/v1/ws and log in with receiveType: "zstd".
  4. Remove the resume logic of the feed channels; reload from /v1/{lang} on snapshot_required instead. See Feed channels.
  5. Handle 4003 as final, and 4004 as a limit.