How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

OddsJam Fixtures API

The Fixtures API from OddsJam — 11 operation(s) for fixtures.

OddsJam Fixtures API is one of 12 APIs that OddsJam publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Fixtures. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an AsyncAPI specification.

This API exposes 11 operations across 11 paths. It is described by OpenAPI 3.1.0, at version 3.0.

Requests are made against a single base URL, https://api.opticodds.com/api/v3.

11 operations 11 paths 0 schemas 9 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
3.0
Server
https://api.opticodds.com/api/v3
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

OddsJam Fixtures API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-Api-Key (ApiKeyHeader). An API key is passed in the query as key (ApiKeyQuery). By default, every request must be authenticated.

Paths & Operations 11

Across 11 paths, the API surfaces 11 operations — 9 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Fixtures 11
GET
/fixtures
List fixtures
→ 200
GET
/fixtures/active
List active fixtures
→ 200
GET
/fixtures/odds
Get odds for fixtures
→ 200
GET
/fixtures/odds/historical
Get historical odds for fixtures
→ 200
GET
/fixtures/results
Get fixture results
→ 200
GET
/fixtures/results/head-to-head
Get head-to-head fixture results
→ 200
GET
/fixtures/player-results
Get player results for fixtures
→ 200
GET
/fixtures/player-results/last-x
Get player results for the last X fixtures
→ 200
POST
/fixtures/results/queue/start
Start fixture results queue
→ 200
POST
/fixtures/results/queue/stop
Stop fixture results queue
→ 200
GET
/fixtures/results/queue/status
Get fixture results queue status
→ 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

oddsjam-fixtures-api-openapi.yml Raw ↑

Other APIs OddsJam publishes across the network.

OddsJam Futures API
OddsJam Grader API
OddsJam Injuries API
OddsJam Leagues API
OddsJam Markets API
OddsJam Players API
OddsJam Sports API
OddsJam Sportsbooks API
OddsJam Streaming API
OddsJam Teams API
OddsJam Tournaments API
Where this information came from

This is an independent, third-party profile of OddsJam Fixtures API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.