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

1Fort Checkout API

Checkout and payment session endpoints.**Access:** public; no authentication required.

1Fort Checkout API is one of 89 APIs that 1Fort publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Checkout. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, authentication docs, and rate-limit docs.

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

Requests are made against a single base URL, https://api.1fort.com/apis/.

11 operations 11 paths 4 schemas 7 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.1fort.com/apis/
Authentication
API Key, API Key
License
Privately owned
Terms of Service
Resource Areas
1

Authentication & Security 2

1Fort Checkout API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (Bearer). An API key is passed in the header as Authorization (ApiKey). By default, every request must be authenticated.

  • Bearer — JWT access token. Send as Bearer or JWT .
  • ApiKey — API key. Send as Api-Key .

Paths & Operations 11

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

checkout 11

Checkout and payment session endpoints. Access: public; no authentication required.

GET
/checkout/invoices
Get invoices by IDs for checkout display.
checkout_invoices_list → 200403500
POST
/checkout/invoices/payment-intent
Create a Stripe PaymentIntent for the given invoices.
checkout_invoices_create_payment_intent → 201403500
POST
/checkout/invoices/search
Search
checkout_invoices_search → 201403500
GET
/checkout/invoices/{id}/pdf
Pdf
checkout_invoices_pdf 1 param → 200403404500
GET
/checkout/invoices/{id}/proposal
Generate and stream the insurance proposal PDF for the quote that backs this CheckoutInvoice.
checkout_invoices_proposal 1 param → 200403404500
GET
/checkout/invoices/{id}/receipt
Receipt
checkout_invoices_receipt 1 param → 200403404500
GET
/checkout/sessions
List Sessions
checkout_sessions_list 4 params → 200403500
GET
/checkout/sessions/{id}
Retrieve Session
checkout_sessions_read 1 param → 200403404500
POST
/checkout/sessions/{id}/stripe-amount
Stripe amount
checkout_sessions_stripe_amount 1 param body → 201400403404500
GET
/checkout/sessions/{id}/stripe-receipt
On-demand Stripe receipt details for the session's completed payment.
checkout_sessions_stripe_receipt 1 param → 200403404500
POST
/checkout/webhook
Create Webhook
checkout_webhook_create → 201403500

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are CheckoutSession (9 properties), GenericError (1 property), APIException (1 property), ValidationError (1 property). Each schema is shown below with its type and property counts.

CheckoutSession
object
9 properties 1 required
ValidationError
object
1 property
APIException
object
1 property 1 required
GenericError
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

1fort-checkout-api-openapi.yml Raw ↑

Other APIs 1Fort publishes across the network.

1Fort agent_runtime (v2) API
1Fort Analytics API
1Fort application: applications API
1Fort application: clients API
1Fort application (v2): applications API
1Fort application (v2): coverages API
1Fort Ascend API
1Fort ascend (v2) API
1Fort Auth API
1Fort Authentication API
1Fort billing (v2) API
1Fort broker: ai-customization-types API
Where this information came from

This is an independent, third-party profile of 1Fort Checkout 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.