AMQPS messaging
Dedicated exchange, TLS, heartbeats and revocable customer credentials.
UOF-compatible delivery
Migrate the feed, not your entire stack.
A delivery profile designed around Unified Odds Feed patterns: encrypted AMQPS, recovery APIs, snapshots, sequencing and operational states under a verifiable technical contract.
AMQPS 5671TLS push transport
REST recoverySnapshots and message replay
Isolated credentialsOne pair per end customer
Explicit statesOpen, suspended, closed, settled
A technical profile built for integration.
Push and recovery are separate, sequence IDs preserve order, and event, market and settlement references travel together. Actual coverage remains governed by the selected plan and signed coverage annex.
Snapshot and replay
API recovery to realign a consumer after connection loss.
Operational states
Open, suspended, closed and settled changes delivered explicitly.
Stable identifiers
LiveFeed IDs are always present; external mappings only when verified.
Server-side entitlements
Sports, leagues, markets and depth filtered before delivery.
Customer monitoring
Connections, usage, limits and revocation visible in the backoffice.
1
Configure the consumer
Use the AMQPS TLS endpoint, virtual host and exchange issued for the integration.
2
Load the snapshot
Import the current catalogue and events through compatible APIs.
3
Apply sequence order
Process updates in order and recover when a sequence gap is detected.
4
Validate settlements
Settle confirmed outcomes only; all other records stay pending.
amqps://<user>:<password>@livefeedapi.com:5671 vhost: /unifiedfeed/<bookmakerId> exchange: unifiedfeed GET /v1/sports GET /v1/schedule/live GET /v1/recovery/messages message.sequenceId message.eventId message.status message.markets[]
Verify coverage before purchase
Sports, markets, results and transports are declared in the coverage matrix and customer order.
“UOF-compatible” describes a compatibility profile developed by LiveFeed API. It does not imply affiliation, certification or full equivalence with third-party products. Migration must be validated against the customer consumer.
Test the flow with isolated credentials.
Start a 14-day developer trial or run a technical session with your integration team.