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

Genius Sports Probabilistic matching API

The results from the this kind of matching are always probabilistic. However we consider matches that have above 90% match score as viable results.

Genius Sports Probabilistic matching API is one of 31 APIs that Genius Sports publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Probabilistic matching. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 36 operations across 24 paths, and defines 54 schemas. It is described by OpenAPI 2.0, at version 2.0.280.

Requests are made against the base URL https://fixtures.api.geniussports.com/v2.

36 operations 24 paths 54 schemas 24 GET12 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
2.0.280
Base URL
https://fixtures.api.geniussports.com/v2
Authentication
API Key, API Key
License
Resource Areas
1

Authentication & Security 2

Genius Sports Probabilistic matching API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (Auth0). An API key is passed in the header as x-api-key (api_key).

Paths & Operations 36

Across 24 paths, the API surfaces 36 operations — 24 GET, 12 POST. Each is listed below with its method, path, parameters, and response codes.

Probabilistic matching 36

The results from the this kind of matching are always probabilistic. However we consider matches that have above 90% match score as viable results.

GET
/competition-matches
Retrieve competition matches by the provided parameters
12 params → 200520400500401413403415
POST
/competition-matches
Retrieve competition matches by the provided parameters, and create a map uppon successful matching.
3 params → 200520400202500401413403
GET
/competition-matches/maps
Retrieve entity maps by source name and source entity id
4 params → 200520400500401413403415
GET
/competitors/doubles-matches
Retrieve double partnerships matches by the provided parameters.
13 params → 200520400500401413403415
POST
/competitors/doubles-matches
Retrieve fixture level players matches by the provided parameters, and create a map uppon successful matching.
3 params → 200520400202500401413403
GET
/competitors/doubles-matches/maps
Retrieve entity maps by source name and source entity id
4 params → 200520400500401413403415
GET
/competitors/player-matches
Retrieve fixture level player matches by the provided parameters.
16 params → 200520400500401413403415
POST
/competitors/player-matches
Retrieve fixture level players matches by the provided parameters, and create a map uppon successful matching.
3 params → 200520400202500401413403
GET
/competitors/player-matches/maps
Retrieve entity maps by source name and source entity id
4 params → 200520400500401413403415
GET
/competitors/team-matches
Retrieve teams matches by the provided parameters.
15 params → 200520400500401413403415
POST
/competitors/team-matches
Retrieve team matches by the provided parameters, and create a map uppon successful matching.
3 params → 200520400202500401413403
GET
/competitors/team-matches/maps
Retrieve entity maps by source name and source entity id
4 params → 200520400500401413403415
GET
/fixture-matches
Retrieve a fixture, within a configurable sport or competition day range
17 params → 200520400500401413403415
POST
/fixture-matches
Retrieve a fixture, best matching to your fixture.
3 params → 200520400202500401413403
GET
/fixture-matches/maps
Retrieve entity maps by source name and source entity id
4 params → 200520400500401413403415
GET
/locality-matches
Retrieve locality matches by the provided parameters
7 params → 200520400500401413403415
POST
/locality-matches
Retrieve locality matches by the provided parameters, and create a map uppon successful matching.
3 params → 200520400202500401413403
GET
/locality-matches/maps
Retrieve entity maps by source name and source entity id
4 params → 200520400500401413403415
GET
/organization-matches
Retrieve a organization
8 params → 200520400500401413403415
POST
/organization-matches
Retrieve a organization, best matching to your organization.
3 params → 200520400202500401413403
GET
/organization-matches/maps
Retrieve entity maps by source name and source entity id
4 params → 200520400500401413403415
GET
/person-matches
Retrieve a person, that can be used in a team squad, as a refferee, coach, etc. The person itself cannot be used in a fixture as a top level competitor. For that use a Player
12 params → 200520400500401413403415
POST
/person-matches
Retrieve a person, that can be used in a team squad, as a refferee, coach, etc., and create a map uppon successful matching.
3 params → 200520400202500401413403
GET
/person-matches/maps
Retrieve entity maps by source name and source entity id
4 params → 200520400500401413403415
GET
/round-matches
Retrieve round matches by the provided parameters
14 params → 200520400500401413403415
POST
/round-matches
Retrieve round matches by the provided parameters, and create a map uppon successful matching.
3 params → 200520400202500401413403
GET
/round-matches/maps
Retrieve entity maps by source name and source entity id
4 params → 200520400500401413403415
GET
/season-matches
Retrieve season matches by the provided parameters
14 params → 200520400500401413403415
POST
/season-matches
Retrieve season matches by the provided parameters, and create a map uppon successful matching.
3 params → 200520400202500401413403
GET
/season-matches/maps
Retrieve entity maps by source name and source entity id
4 params → 200520400500401413403415
GET
/sport-matches
Retrieve sport matches by the provided parameters
7 params → 200520400500401413403415
POST
/sport-matches
Retrieve sport matches by the provided parameters, and create a map uppon successful matching.
3 params → 200520400202500401413403
GET
/sport-matches/maps
Retrieve entity maps by source name and source entity id
4 params → 200520400500401413403415
GET
/venue-matches
Retrieve a venue
11 params → 200520400500401413403415
POST
/venue-matches
Retrieve a venue, best matching to your venue.
3 params → 200520400202500401413403
GET
/venue-matches/maps
Retrieve entity maps by source name and source entity id
4 params → 200520400500401413403415

Schemas 54

The contract defines 54 schemas that model the data the API accepts and returns. The most detailed are entityMapResponse (10 properties), organizationMatchHATEOASResultModel (9 properties), personMatchHATEOASResultModel (9 properties), fixtureMatchHATEOASResultModel (9 properties). Each schema is shown below with its type and property counts.

personRequest
organizationMatchHATEOASResultModel
object
9 properties 3 required
baseMatchModel
object
4 properties 1 required
Error
object
4 properties 3 required
personMatchRequest
roundMatchRequest
localityMatchHATEOASResultModel
object
9 properties 3 required
doublesMatchHATEOASResultModel
object
9 properties 3 required
personMatch
object
4 properties 1 required
entityMatchReference
object
3 properties
doublesMatch
object
4 properties 1 required
entityRelation
object
2 properties
dataSourceReference
object
3 properties
competitionMatchRequest
doublesMatchRequest
BadRequestModel
object
1 property
fixtureMatch
object
4 properties 1 required
seasonMatch
object
4 properties 1 required
organization
string
If sent а FUZZY match is made on the value and the similarity score is contributing to the end match score.
roundMatchHATEOASResultModel
object
9 properties 3 required
sportMatchRequest
object
2 properties 1 required
ArrayOfentityMapResponse
array
playerMatchHATEOASResultModel
object
9 properties 3 required
failedMatchResponse
object
3 properties 2 required
sportMatchHATEOASResultModel
object
9 properties 3 required
teamMatchRequest
ErrorModel
object
3 properties
teamMatch
object
4 properties 1 required
matchResultSubsribableModel
object
4 properties
playerMatch
object
4 properties 1 required
playerMatchRequest
localityMatch
object
4 properties 1 required
ageCategory
string
If sent an EXACT match is made on the enum, excluding all non-matching entities.
competitionMatchHATEOASResultModel
object
9 properties 3 required
competition
string
If the competition is sent as string name a FUZZY match is made on the value and the similarity score is contributing to the end match score.
locality
string
If sent а FUZZY match is made on the value and the similarity score is contributing to the end match score.
venueMatchRequest
entityMapResponse
object
10 properties
sportMatch
object
4 properties 1 required
fixtureMatchRequest
organizationMatchRequest
seasonMatchRequest
seasonMatchHATEOASResultModel
object
9 properties 3 required
season
string
If the season is sent as string name a FUZZY match is made on the value and the similarity score is contributing to the end match score.
venueMatchHATEOASResultModel
object
9 properties 3 required
teamMatchHATEOASResultModel
object
9 properties 3 required
venueMatch
object
4 properties 1 required
gender
string
If sent an EXACT match is made on the enum, excluding all non-matching entities.
roundMatch
object
4 properties 1 required
fixtureMatchHATEOASResultModel
object
9 properties 3 required
personMatchHATEOASResultModel
object
9 properties 3 required
localityMatchRequest
object
2 properties 1 required
competitionMatch
object
4 properties 1 required
organizationMatch
object
4 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

genius-sports-probabilistic-matching-api-openapi.yml Raw ↑

Other APIs Genius Sports publishes across the network.

Genius Sports REST API
Genius Sports Streaming API
Genius Sports Publish API
Genius Sports LiveStats In-Arena Feed
Genius Sports Licensing API
Genius Sports Competitions API
Genius Sports Competitors API
Genius Sports competitors/doubles API
Genius Sports competitors/horses API
Genius Sports competitors/players API
Genius Sports competitors/tbds API
Genius Sports competitors/teams API
Where this information came from

This is an independent, third-party profile of Genius Sports Probabilistic matching 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.