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

ParlayAPI Historical API

The Historical API from ParlayAPI — 13 operation(s) for historical.

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

Tagged areas include Historical. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, pricing, an AsyncAPI specification, and rate-limit docs.

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

Requests are made against 2 base URLs: https://parlay-api.com, https://api.parlay-api.com.

14 operations 13 paths 2 schemas 1 DELETE12 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.2.0
Base URL
https://api.parlay-api.com
Authentication
API Key, API Key, HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 3

ParlayAPI Historical API declares 3 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 apiKey (apiKeyQuery). It accepts HTTP bearer tokens (APIKey) (bearerAuth).

  • apiKeyHeader — API key passed in the X-API-Key header. Recommended.
  • apiKeyQuery — API key passed as the ?apiKey= query parameter. Useful for browser fetch() and webhooks where header control is limited. Equivalent to X-API-Key.
  • bearerAuth — API key passed via Authorization: Bearer . Equivalent to X-API-Key for compatibility with auth libraries that expect bearer tokens.

Paths & Operations 14

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

Historical 14

Historical odds archive (game closing lines from 2005), closing lines, and period markets.

GET
/v1/historical/sports/{sport_key}/period_markets
Historical Period Markets
historical_period_markets_v1_historical_sports__sport_key__period_markets_get 12 params → 200422
GET
/v1/historical/sports/{sport_key}/odds
Get Historical Odds
get_historical_odds_v1_historical_sports__sport_key__odds_get 5 params → 200422
GET
/v1/historical/sports/{sport_key}/matches
Get Historical Matches
get_historical_matches_v1_historical_sports__sport_key__matches_get 8 params → 200422
GET
/v1/historical/sports/{sport_key}/coverage
Get Historical Coverage
get_historical_coverage_v1_historical_sports__sport_key__coverage_get 3 params → 200422
GET
/v1/historical/prediction-markets/crypto/{asset}
Get Crypto Prediction Markets Historical
get_crypto_prediction_markets_historical_v1_historical_prediction_markets_crypto__asset__get 6 params → 200422
GET
/v1/historical/sports/{sport_key}/closing-odds
Get Historical Closing Odds
get_historical_closing_odds_v1_historical_sports__sport_key__closing_odds_get 12 params → 200422
POST
/v1/historical/closing-lines/import
Import Customer Closing Lines
import_customer_closing_lines_v1_historical_closing_lines_import_post body → 200422
DELETE
/v1/historical/closing-lines/import
Delete Customer Closing Imports
delete_customer_closing_imports_v1_historical_closing_lines_import_delete 2 params → 200422
GET
/v1/historical/coverage
Historical Coverage
historical_coverage_v1_historical_coverage_get 3 params → 200422
GET
/v1/historical/stats
Get Historical Stats
get_historical_stats_v1_historical_stats_get → 200
GET
/v1/historical/source-quality.csv
Historical Source Quality Csv
historical_source_quality_csv_v1_historical_source_quality_csv_get 2 params → 200422
GET
/v1/historical/source-quality.json
Historical Source Quality Json
historical_source_quality_json_v1_historical_source_quality_json_get 2 params → 200422
GET
/v1/historical/closing-lines.json
Closing Lines Json
closing_lines_json_v1_historical_closing_lines_json_get 4 params → 200422
GET
/v1/historical/closing-lines.csv
Closing Lines Csv
closing_lines_csv_v1_historical_closing_lines_csv_get 4 params → 200422

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are ValidationError (5 properties), HTTPValidationError (1 property). Each schema is shown below with its type and property counts.

HTTPValidationError
object
1 property
ValidationError
object
5 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

parlay-api-historical-api-openapi.yml Raw ↑

Other APIs ParlayAPI publishes across the network.

ParlayAPI Acceptable Use API
ParlayAPI Account API
ParlayAPI Affiliates API
ParlayAPI Agent API
ParlayAPI Alerts API
ParlayAPI Auth API
ParlayAPI Badge API
ParlayAPI Billing API
ParlayAPI Calculators API
ParlayAPI Changelog.json API
ParlayAPI Clv API
ParlayAPI Collections API
Where this information came from

This is an independent, third-party profile of ParlayAPI Historical 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.