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

Dodo Payments Checkout Sessions API

The Checkout Sessions API from Dodo Payments — 2 operation(s) for checkout sessions.

Dodo Payments Checkout Sessions API is one of 12 APIs that Dodo Payments publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Checkout Sessions. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

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

Requests are made against 2 base URLs: https://live.dodopayments.com, https://test.dodopayments.com.

2 operations 2 paths 5 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://live.dodopayments.com
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

Dodo Payments Checkout Sessions API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Authenticate with your Dodo Payments API key as a bearer token: Authorization: Bearer YOURAPIKEY. Use a test-mode key against https://test.dodopayments.com and…

Paths & Operations 2

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

Checkout Sessions 2
POST
/checkouts
Create a checkout session
createCheckoutSession body → 200
GET
/checkouts/{session_id}
Get a checkout session
getCheckoutSession 1 param → 200

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are CreateCheckoutSessionRequest (6 properties), BillingAddress (5 properties), CheckoutSession (4 properties), CustomerRequest (4 properties). Each schema is shown below with its type and property counts.

CheckoutSessionProductCartItem
object
3 properties 2 required
CustomerRequest
object
Either an existing customer reference (customerid) or new customer details (email, name) used to attach a payment or subscription.
4 properties
CreateCheckoutSessionRequest
object
6 properties 1 required
CheckoutSession
object
4 properties
BillingAddress
object
5 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

dodo-payments-checkout-sessions-api-openapi.yml Raw ↑

Other APIs Dodo Payments publishes across the network.

Dodo Payments Customers API
Dodo Payments Discounts API
Dodo Payments Disputes API
Dodo Payments License Keys API
Dodo Payments Licenses API
Dodo Payments Payments API
Dodo Payments Payouts API
Dodo Payments Products API
Dodo Payments Refunds API
Dodo Payments Subscriptions API
Dodo Payments Webhooks API
Where this information came from

This is an independent, third-party profile of Dodo Payments Checkout Sessions 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.