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

The Metadata API from ParlayAPI — 34 operation(s) for metadata.

ParlayAPI Metadata 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 Metadata. 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 34 operations across 34 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.

34 operations 34 paths 2 schemas 32 GET2 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 Metadata 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 34

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

Metadata 34

Machine-readable platform metadata: pricing, SLA, incidents, uptime, credit costs.

GET
/v1/meta/api-info
Api Info
api_info_v1_meta_api_info_get → 200
GET
/v1/meta/credit-costs
Credit Costs
credit_costs_v1_meta_credit_costs_get → 200
POST
/v1/meta/quote
Quote Credits
quote_credits_v1_meta_quote_post body → 200422
POST
/v1/meta/batch-quote
Batch Quote Credits
batch_quote_credits_v1_meta_batch_quote_post body → 200422
GET
/v1/meta/sla
Get Sla
get_sla_v1_meta_sla_get → 200
GET
/v1/meta/sdks
Get Sdks
get_sdks_v1_meta_sdks_get → 200
GET
/v1/meta/source-capabilities
Source Capabilities
source_capabilities_v1_meta_source_capabilities_get → 200
GET
/v1/meta/endpoints
List Endpoints
list_endpoints_v1_meta_endpoints_get 2 params → 200422
GET
/v1/meta/webhooks
Webhooks Spec
webhooks_spec_v1_meta_webhooks_get → 200
GET
/v1/meta/provider-state
Provider State
provider_state_v1_meta_provider_state_get → 200
GET
/v1/meta/source-quality
Source Quality
source_quality_v1_meta_source_quality_get 2 params → 200422
GET
/v1/meta/source-health
Source Health Alias
source_health_alias_v1_meta_source_health_get 2 params → 200422
GET
/v1/meta/collector-flush
Collector Flush Meta
collector_flush_meta_v1_meta_collector_flush_get → 200
GET
/v1/meta/latest-state
Latest State Meta
latest_state_meta_v1_meta_latest_state_get 2 params → 200422
GET
/v1/meta/per-book-sla
Meta Per Book Sla
meta_per_book_sla_v1_meta_per_book_sla_get → 200
GET
/v1/meta/parser-coverage
Meta Parser Coverage
meta_parser_coverage_v1_meta_parser_coverage_get 3 params → 200422
GET
/v1/meta/book-coverage
Meta Book Coverage
meta_book_coverage_v1_meta_book_coverage_get 2 params → 200422
GET
/v1/pricing
Get Pricing
get_pricing_v1_pricing_get → 200
GET
/v1/status
Status Json
status_json_v1_status_get → 200
GET
/v1/status/history
Status History
status_history_v1_status_history_get 2 params → 200422
GET
/v1/usage
Get Usage
get_usage_v1_usage_get 1 param → 200422
GET
/v1/meta/movers
Meta Movers
meta_movers_v1_meta_movers_get 4 params → 200422
GET
/v1/meta/limits
Meta Limits
meta_limits_v1_meta_limits_get → 200
GET
/v1/meta/api-key-check
Meta Api Key Check
meta_api_key_check_v1_meta_api_key_check_get → 200
GET
/v1/meta/usage
Meta Usage
meta_usage_v1_meta_usage_get 1 param → 200422
GET
/v1/meta/diagnostic
Meta Diagnostic
meta_diagnostic_v1_meta_diagnostic_get → 200
GET
/v1/meta/status-history.json
Meta Status History Json
meta_status_history_json_v1_meta_status_history_json_get 1 param → 200422
GET
/v1/meta/book-catalog
Meta Book Catalog
meta_book_catalog_v1_meta_book_catalog_get 3 params → 200422
GET
/v1/meta/event-search
Meta Event Search
meta_event_search_v1_meta_event_search_get 4 params → 200422
GET
/v1/meta/markets
Meta Markets
meta_markets_v1_meta_markets_get → 200
GET
/v1/meta/regions
Meta Regions
meta_regions_v1_meta_regions_get → 200
GET
/v1/meta/changelog
Meta Changelog Json
meta_changelog_json_v1_meta_changelog_get 1 param → 200422
GET
/v1/meta/incidents
Incidents Json
incidents_json_v1_meta_incidents_get 3 params → 200422
GET
/v1/meta/uptime
Uptime Stats
uptime_stats_v1_meta_uptime_get 3 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-metadata-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 Metadata 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.