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 Rounds API

The Rounds API from Genius Sports — 5 operation(s) for rounds.

Genius Sports Rounds 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 Rounds. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 13 operations across 5 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version 2.0.280.

Requests are made against a single base URL, https://fixtures.api.geniussports.com/v2.

13 operations 5 paths 18 schemas 3 DELETE3 GET3 OPTIONS1 PATCH2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.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 Rounds 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 13

Across 5 paths, the API surfaces 13 operations — 3 DELETE, 3 GET, 3 OPTIONS, 1 PATCH, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Rounds 13
OPTIONS
/rounds
Describe rounds
optionsRounds → 200
GET
/rounds
Retrieve rounds by ID/s. MAX 200 per page
getRounds 5 params → 200520400500401413403415
POST
/rounds
Create new round
postRounds 2 params body → 520201400202500404504429
PUT
/rounds
Update existing round
putRounds 2 params body → 200520400202500404504409
PATCH
/rounds
Patch existing round
patchRounds 2 params body → 200520400202500404504409
OPTIONS
/rounds/{id}
Describe rounds by id
optionsRoundsById 1 param → 200
GET
/rounds/{id}
Retrieve rounds details by ID
getRoundsById 2 params → 200520400202500401413403
DELETE
/rounds/{id}
Delete existing round
deleteRoundsById 3 params → 200520400202500404504
OPTIONS
/rounds/{id}/competitors
Describe rounds by id competitors
optionsRoundsByIdCompetitors 1 param → 200
GET
/rounds/{id}/competitors
Retrieve round competitors by Round ID/s. MAX 200 per page
getRoundsByIdCompetitors 6 params → 200520400500401413403415
POST
/rounds/{id}/competitors
Adds new competitor to the round
postRoundsByIdCompetitors 3 params body → 520201400202500404504429
DELETE
/groups/{id}
Delete existing round
deleteGroupsById 3 params → 200520400202500404504
DELETE
/rounds/{id}/competitors/{competitorId}
Removes competitor added to round
deleteRoundsByIdCompetitorsByCompetitorId 4 params → 200520400202500404504

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are RoundResponseModel (15 properties), UpdateRound (9 properties), RoundCompetitorsResponseModelHATEOASReponseModel (9 properties), CreateRound (9 properties). Each schema is shown below with its type and property counts.

Empty
object
JsonbModelViewModel
object
This model should be used to create or update single property value for specific property name for specific model.
2 properties 1 required
JsonbModel
object
3 properties
UpdateRound
object
This model should be used to update a round object.
9 properties 7 required
CreateRound
object
This model should be used to create a round object.
9 properties 6 required
BadRequestModel
object
1 property
PatchRound
object
This model should be used to propose a partial update/patch to a round.
3 properties 1 required
RoundCompetitorsResponseModel
object
6 properties 6 required
AcceptedModel
object
1 property
RoundResponseModel
object
15 properties 10 required
ExternalIdsViewModel
object
External system identifiers. Key represents the external system name (e.g., 'optaId', 'optaLegacyId', 'fibaId', 'vesselId','statsEngineId'), value represents t…
5 properties
Error
object
5 properties 3 required
ErrorDuplicateModel
object
2 properties
RoundResponseModelHATEOASReponseModel
object
9 properties
ErrorModel
object
3 properties
CreateRoundCompetitor
object
1 property
RoundCompetitorsResponseModelHATEOASReponseModel
object
9 properties
HALEmbededResponse
object
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

genius-sports-rounds-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 Rounds 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.