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

The clv API from ParlayAPI — 1 operation(s) for clv.

ParlayAPI Clv 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 clv. 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 1 operation across 1 path, and defines 3 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.

1 operations 1 paths 3 schemas 1 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 Clv 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 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

clv 1
POST
/v1/clv/import-screenshot
Import Bet Screenshot
import_bet_screenshot_v1_clv_import_screenshot_post body → 200422

Schemas 3

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

HTTPValidationError
object
1 property
Body_import_bet_screenshot_v1_clv_import_screenshot_post
object
1 property
ValidationError
object
5 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

parlay-api-clv-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 Collections API
ParlayAPI Dashboard API
Where this information came from

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