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

Server-side operations for authorizing Affirm transactions after a customer completes the checkout flow and a checkout token is returned.

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

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

This API exposes 3 operations across 3 paths, and defines 3 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.

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

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

Authorization 3

Server-side operations for authorizing Affirm transactions after a customer completes the checkout flow and a checkout token is returned.

POST
/transactions
Affirm Authorize a Transaction
authorizeDirectTransaction body → 200400401
POST
/files
Affirm Upload a File
uploadFile body → 200400401
GET
/files/{id}
Affirm Download a File
downloadFile 1 param → 200401404

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Transaction (9 properties), FileObject (6 properties), Error (3 properties). Each schema is shown below with its type and property counts.

FileObject
object
Represents a file uploaded to Affirm's servers.
6 properties
Error
object
Standard error response returned by the Affirm API.
3 properties
Transaction
object
Represents an Affirm payment transaction at any point in its lifecycle.
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

affirm-authorization-api-openapi.yml Raw ↑

Other APIs Affirm publishes across the network.

Affirm Checkout API
Affirm Charges API
Affirm Transactions API
Affirm Cards API
Affirm Checkouts 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 Authorization 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.