Early access. The API opens with the platform. Contact contact@apexiumbet.com for access, and for a test environment while you integrate.
What is the Apexium API?
The Apexium API is the programmatic access to your apexiumbet.com account. Everything you do through it happens on that account, with the same balance, the same bookmakers and the same rules as in the dashboard.- Execution: read the betslip for your price and stake limits, preview an order, place it, follow its bets until they settle, and cancel what is still working.
- Account: read your balance, your open positions and your realised PnL.
- Market data: read fixtures, scores and odds from OddsPapi v5, limited to your bookmakers.
fixtureId and outcomeId you read in the odds are the ones you place orders on, so there is no mapping layer between your data and your execution. An OddsPapi client only changes its base URL and its key; see Market data and identifiers.
An order is your instruction: back an outcome for a stake, at or above a minimum price. Apexium splits it into bets at one or more bookmakers. You follow the order and its bets through the same endpoints, whether you placed it through the API or from the dashboard.
Environments
Every endpoint lives under
/v1. A test environment, with its own base URL and keys, is available on request while you integrate. Keys only work in the environment that issued them.
Where to start
Quickstart
From a key to a placed order in five calls.
Authentication
Get a key, send it, rotate it.
Preview and place
What an order asks for, and what you get back.
Market data and identifiers
OddsPapi v5 sports, fixtures, markets and odds, and how they become orders.
API reference
Every endpoint, generated from the API’s contract and the OddsPapi v5 reference.
How the reference is built
The endpoint pages are generated from the OpenAPI contract that the API itself exports, and the market data pages from the OddsPapi v5 reference. A field, a parameter or a status code is in the reference because the API has it. The/v1 contract only grows: fields, endpoints and enum values are added, never renamed or removed, so handle unknown enum values gracefully.