Bolt Embeddable Checkout v3 API
The v3 generation of the Bolt Embeddable Checkout API, served under a /v3 path with a templated environment server variable. Reorganises the surface around Accounts, Payments (including guest payments), Orders, OAuth, merchant Callbacks, Testing and Events. Bolt gates v3 behind explicit enablement and directs most integrations to v1.
Bolt Embeddable Checkout v3 API is one of 5 APIs that Bolt Financial publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Checkout, Payments, Order, and Account. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes 16 operations across 15 paths, organized into 6 resource areas, and defines 77 schemas. It is described by OpenAPI 3.0.0, at version 3.3.22.
Requests are made against a single base URL, https://{environment}.boltapp.com/v3.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Bolt Embeddable Checkout v3 API declares
2 security schemes
for authenticating requests.
An API key is passed in the header as X-API-Key (api-key).
It supports OAuth 2.0 (oauth) using the authorizationCode flow, exposing 3 scopes.
Paths & Operations 16
Across 15 paths, the API surfaces 16 operations — 2 DELETE, 2 GET, 11 POST, 1 PUT. They span 6 resource areas: Account, Payments, Orders, OAuth, Callbacks, Testing. Each is listed below with its method, path, parameters, and response codes.
Use the Accounts API to access shoppers' accounts to empower your checkout and facilitate shoppers' choices.
Use the Payments API to process credit card and alternative payment methods with Bolt.
Use the Orders API to create and manage orders, including orders that have been placed outside the Bolt ecosystem.
Use the OAuth API to enable your ecommerce server to make API calls on behalf of a Bolt logged-in shopper.
Implement Callback endpoints on your servers to power Bolt experiences. Different Bolt packages require different callbacks to be implemented. Consult your relevant product docume…
Use the Testing API to generate and retrieve test data to verify a subset of flows in non-production environments.
Schemas 77
The contract defines 77 schemas that model the data the API accepts and returns. The most detailed are address-reference-explicit (13 properties), address-listing (13 properties), account-test-creation-data (9 properties), cart-item (9 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Bolt Financial 4
Other APIs Bolt Financial publishes across the network.
This is an independent, third-party profile of Bolt Embeddable Checkout v3 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.