Affirm
Affirm is a buy-now-pay-later platform offering installment loans at point-of-sale via merchant SDKs and direct APIs. Public Series A through F-funded company.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Affirm the way a machine reads it — 124 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Affirm scores 37.3/100 (thin), with a separate agent-readiness read of 28/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Affirm's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/affirm/"
title="Affirm on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/affirm.svg"
alt="Affirm Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/affirm/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/affirm/"
title="Affirm on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/affirm/card.svg"
alt="Affirm Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Affirm
Each block below is one kind of artifact we hold for Affirm. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 11
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Affirm Checkout API
Initialize and authorize Affirm checkout flows for online merchants.
Affirm Charges API
Capture, void, and refund Affirm charges; read transaction details.
Affirm Transactions API
Read transactions, settlements, and disputes.
Affirm Authorization API
Server-side operations for authorizing Affirm transactions after a customer completes the checkout flow and a checkout token is returned.
Affirm Cards API
Operations for managing virtual card numbers (VCN) issued via the Affirm Lite integration pattern.
Affirm Checkouts API
Operations for creating, retrieving, updating, and resending Affirm checkout sessions.
Affirm Disputes API
Operations for listing, retrieving, contesting, and closing payment disputes initiated by customers.
Affirm Promos API
Operations for retrieving dynamic promotional messaging and financing term information to display on merchant web pages.
Affirm Settlement Events API
Operations for listing settlement events and summaries that track disbursement activity.
Affirm Transaction Events API
Operations for listing transaction event records associated with transaction lifecycle changes.
Affirm Transactions API
Post-authorization transaction management operations including capture, void, and refund.
Scroll within the panel for all 11 ·
Open Collections 14
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONAffirm Checkout Authorization API
OPEN COLLECTIONAffirm Checkout Authorization Cards API
OPEN COLLECTIONAffirm Checkout API
OPEN COLLECTIONAffirm Checkout Authorization Checkouts API
OPEN COLLECTIONAffirm Direct API
OPEN COLLECTIONAffirm Checkout Authorization Disputes API
OPEN COLLECTIONAffirm Disputes API
OPEN COLLECTIONAffirm Checkout Authorization Promos API
OPEN COLLECTIONAffirm Promos API
OPEN COLLECTIONAffirm Checkout Authorization Settlement Events API
OPEN COLLECTIONAffirm Checkout Authorization Transaction Events API
OPEN COLLECTIONAffirm Checkout Authorization Transactions API
OPEN COLLECTIONAffirm Transactions API
OPEN COLLECTIONScroll within the panel for all 14 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Affirm GraphQL Schema
This document describes the conceptual GraphQL schema for the Affirm Buy Now Pay Later (BNPL) platform. Affirm's production API is REST-based; this schema models the same domain...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Affirm Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Affirm Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Affirm Finops
FINOPSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Affirm Webhooks
Affirm uses webhooks to notify merchant endpoints in real time when events occur during the customer checkout and prequalification flows. Webhooks are available to Key and Enter...
ASYNCAPISemantic Vocabularies 6
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Affirm Checkout Context
JSON-LDAffirm Context
JSON-LDAffirm Direct Context
JSON-LDAffirm Disputes Context
JSON-LDAffirm Promos Context
JSON-LDAffirm Transactions Context
JSON-LDSpectral Rules 3
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JSON Schema 27
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Affirm Checkout
JSON SCHEMAAffirm Dispute
JSON SCHEMAAffirm Transaction
JSON SCHEMAAddressObject
JSON SCHEMACheckoutRequest
JSON SCHEMACheckout
JSON SCHEMAContactObject
JSON SCHEMADiscountObject
JSON SCHEMAItemObject
JSON SCHEMAMerchantObject
JSON SCHEMANameObject
JSON SCHEMAStoreObject
JSON SCHEMACard
JSON SCHEMAFileObject
JSON SCHEMATransaction
JSON SCHEMADispute
JSON SCHEMAEvidenceItem
JSON SCHEMAEvidenceRequest
JSON SCHEMAFinancingTerm
JSON SCHEMAOfferContent
JSON SCHEMAPromoConfig
JSON SCHEMAPromoContent
JSON SCHEMAPromoResponse
JSON SCHEMASettlementEvent
JSON SCHEMASettlementEventSummary
JSON SCHEMATransactionEvent
JSON SCHEMATransaction
JSON SCHEMAScroll within the panel for all 27 ·
JSON Structure 27
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Affirm Checkout Structure
JSON STRUCTUREAffirm Dispute Structure
JSON STRUCTUREAffirm Transaction Structure
JSON STRUCTURECheckout Address Object Structure
JSON STRUCTURECheckout Checkout Request Structure
JSON STRUCTURECheckout Checkout Structure
JSON STRUCTURECheckout Contact Object Structure
JSON STRUCTURECheckout Discount Object Structure
JSON STRUCTURECheckout Item Object Structure
JSON STRUCTURECheckout Merchant Object Structure
JSON STRUCTURECheckout Name Object Structure
JSON STRUCTURECheckout Store Object Structure
JSON STRUCTUREDirect Api Card Structure
JSON STRUCTUREDirect Api File Object Structure
JSON STRUCTUREDirect Api Transaction Structure
JSON STRUCTUREDisputes Dispute Structure
JSON STRUCTUREDisputes Evidence Item Structure
JSON STRUCTUREDisputes Evidence Request Structure
JSON STRUCTUREPromos Financing Term Structure
JSON STRUCTUREPromos Offer Content Structure
JSON STRUCTUREPromos Promo Config Structure
JSON STRUCTUREPromos Promo Content Structure
JSON STRUCTUREPromos Promo Response Structure
JSON STRUCTURETransactions Settlement Event Structure
JSON STRUCTURETransactions Settlement Event Summary Structure
JSON STRUCTURETransactions Transaction Event Structure
JSON STRUCTURETransactions Transaction Structure
JSON STRUCTUREScroll within the panel for all 27 ·
Examples 27
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Affirm Checkout Example
EXAMPLEAffirm Dispute Example
EXAMPLEAffirm Transaction Example
EXAMPLECheckout Checkout Example
EXAMPLECheckout Item Object Example
EXAMPLECheckout Name Object Example
EXAMPLEDirect Api Card Example
EXAMPLEDisputes Dispute Example
EXAMPLEPromos Offer Content Example
EXAMPLEPromos Promo Config Example
EXAMPLEPromos Promo Content Example
EXAMPLEScroll within the panel for all 27 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Affirm — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/affirm · machine-readable index on apis.io
This is an independent, third-party profile of Affirm, 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.