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

Affirm Checkouts API

Operations for creating, retrieving, updating, and resending Affirm checkout sessions.

Affirm Checkouts API is one of 11 APIs that Affirm publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Checkouts. The published artifact set on APIs.io includes an OpenAPI specification.

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

Requests are made against 2 base URLs: https://api.affirm.com/api/v1, https://sandbox.affirm.com/api/v1.

5 operations 4 paths 10 schemas 1 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.affirm.com
Authentication
HTTP Basic
Terms of Service
Resource Areas
1

Authentication & Security 1

Affirm Checkouts API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • basicAuth — HTTP Basic Authentication using the merchant's public API key as the username and private API key as the password, Base64-encoded as per RFC 7617.

Paths & Operations 5

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

Checkouts 5

Operations for creating, retrieving, updating, and resending Affirm checkout sessions.

POST
/checkouts
Affirm Store a Checkout
storeCheckout body → 200400401
POST
/checkouts/direct
Affirm Direct Checkout
directCheckout body → 200400401
GET
/checkouts/{token}
Affirm Read a Checkout
readCheckout 1 param → 200401404
POST
/checkouts/{token}
Affirm Update a Checkout
updateCheckout 1 param body → 200400401404
POST
/checkouts/{token}/resend
Affirm Resend a Checkout
resendCheckout 1 param body → 200400401404

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are Checkout (18 properties), CheckoutRequest (15 properties), ItemObject (7 properties), AddressObject (6 properties). Each schema is shown below with its type and property counts.

MerchantObject
object
Merchant-specific configuration for the checkout, including callback URLs and the public API key.
5 properties 2 required
CheckoutRequest
object
Request body for creating or updating an Affirm checkout session, containing all order and customer information required to initiate the Affirm financing flow.
15 properties 4 required
ItemObject
object
Represents a single line item in the checkout, including product details and pricing.
7 properties 4 required
DiscountObject
object
Represents a discount applied to the checkout.
2 properties
StoreObject
object
Address details for in-store transactions where the purchase is made at a physical merchant location.
2 properties
ContactObject
object
Contact information for shipping or billing, including name, address, email, and phone number.
4 properties
AddressObject
object
A postal address.
6 properties
Checkout
object
Represents an Affirm checkout session with full order details, customer information, and current checkout status.
18 properties
Error
object
Standard error response returned by the Affirm API.
4 properties
NameObject
object
A person's name split into first and last components.
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

affirm-checkouts-api-openapi.yml Raw ↑

Other APIs Affirm publishes across the network.

Affirm Checkout API
Affirm Charges API
Affirm Transactions API
Affirm Authorization API
Affirm Cards API
Affirm Disputes API
Affirm Promos API
Affirm Settlement Events API
Affirm Transaction Events API
Affirm Transactions API
Where this information came from

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