Concepts Overview

Vertex is the B2B odds delivery API of a quantitative sports betting syndicate and odds provider. It gives external clients programmatic access to proprietary pricing across a broad range of sports (soccer, tennis, basketball, baseball, ice hockey, American football, combat sports such as MMA and boxing, esports, and many more), delivered as both REST catalog endpoints and a real-time WebSocket feed. The full, current set of sports is returned by the /sports endpoint.

This section explains the foundational concepts you need to consume the feed effectively. We recommend reading these pages in order before integrating.

The Vertex price

The API exposes prices from a single pricing provider: Vertex (pricing_provider_id: 1). Every selection carries one Vertex price, and pricing_provider_id is always 1 wherever it appears in the API.

Data hierarchy at a glance

All odds in the feed are organised under a strict five-level hierarchy:

Every entity has a stable integer identifier, and each level references its parent by id (sport_id, competition_id, event_id, market_id). See Data Hierarchy for the full model.

How REST and WebSocket relate

The API is split into two transports with complementary roles:

Transport	Role	Use for
REST	Catalog and current state	Discovering sports, competitions, events, and markets; fetching current prices for an event; re-establishing state after a connection loss
WebSocket	Real-time updates	Receiving live price changes, market status transitions, and event lifecycle updates as they happen

The standard integration pattern is: use REST to bootstrap your catalog and load current prices, then open a WebSocket subscription to receive updates. On reconnect, re-subscribe and re-baseline from REST. The feed does not replay messages missed while you were disconnected (see Reconnecting).

Where to go next

• Data Hierarchy: the Sport → Selection model and how identifiers work
• Stake Limits: how min_stake / max_stake work and how the maximum stake depends on price