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

The billing API from ParlayAPI — 9 operation(s) for billing.

ParlayAPI Billing 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 Billing. 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 10 operations across 9 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.

10 operations 9 paths 2 schemas 5 GET5 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 Billing 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 10

Across 9 paths, the API surfaces 10 operations — 5 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Billing 10
POST
/billing/checkout
Create Checkout
create_checkout_billing_checkout_post 2 params → 200422
POST
/billing/portal
Create Portal
create_portal_billing_portal_post → 200
GET
/billing/portal
Open Portal Via Token
open_portal_via_token_billing_portal_get 1 param → 200422
POST
/billing/subscription/cancel
Cancel Subscription Route
cancel_subscription_route_billing_subscription_cancel_post → 200
POST
/billing/portal/send-link
Admin Send Portal Link
admin_send_portal_link_billing_portal_send_link_post 2 params → 200422
POST
/billing/portal/revoke
Admin Revoke Portal Link
admin_revoke_portal_link_billing_portal_revoke_post 2 params → 200422
GET
/billing/success
Checkout Success
checkout_success_billing_success_get 1 param → 200422
GET
/billing/success-page
Checkout Success Page Alias
checkout_success_page_alias_billing_success_page_get 1 param → 200422
GET
/billing/cancel
Checkout Cancel
checkout_cancel_billing_cancel_get → 200
GET
/billing/cancel-page
Checkout Cancel Page Alias
checkout_cancel_page_alias_billing_cancel_page_get → 200

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-billing-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 Calculators API
ParlayAPI Changelog.json API
ParlayAPI Clv API
ParlayAPI Collections API
ParlayAPI Dashboard API
Where this information came from

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