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

Bolt Payments API

Use the Payments API to process credit card and alternative payment methods with Bolt.

Bolt Payments API is one of 13 APIs that Bolt publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 4 operations across 4 paths, and defines 44 schemas. It is described by OpenAPI 3.0.0, at version 3.3.22.

Requests are made against a single base URL, https://{environment}.bolt.com/v3.

4 operations 4 paths 44 schemas 4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
3.3.22
Base URL
https://api.bolt.com
Authentication
API Key, OAuth 2.0
Contact
Terms of Service
Resource Areas
1

Authentication & Security 2

Bolt Payments 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 4

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

Payments 4

Use the Payments API to process credit card and alternative payment methods with Bolt.

POST
/payments
Initialize a Bolt payment for logged in shoppers
paymentsInitialize 2 params body → 2004XXdefault
POST
/payments/{id}
Finalize a pending payment
paymentsAction 3 params body → 2004XXdefault
POST
/guest/payments
Initialize a Bolt payment for guest shoppers
guestPaymentsInitialize 2 params body → 2004XXdefault
POST
/guest/payments/{id}
Finalize a pending guest payment
guestPaymentsAction 3 params body → 2004XXdefault

Schemas 44

The contract defines 44 schemas that model the data the API accepts and returns. The most detailed are address-reference-explicit (13 properties), cart-item (9 properties), cart (8 properties), guest-payment-initialize-request (7 properties). Each schema is shown below with its type and property counts.

cart-discount
object
3 properties 1 required
payment-initialize-request
object
6 properties 2 required
marketplace-commission-fee
object
3 properties
seller-split
object
3 properties
payment-response-three-ds-required
object
4 properties 3 required
seller-split-amounts
object
5 properties
processor-response
object
Raw authorization response from the payment processor
3 properties
address-reference-partial
object
2 properties 2 required
payment-method-klarna-paynow
object
2 properties 2 required
cart
object
8 properties 3 required
payment-method-googlepay
payment-response-pending
object
5 properties 4 required
payment-method-affirm
object
2 properties 2 required
address-reference
payment-method-afterpay
object
2 properties 2 required
payment-method-reference
object
2 properties 2 required
credit-card
object
7 properties 5 required
payment-response-finalized
object
4 properties 3 required
field-error
object
An error that pertains to validation of a specific field in the request.
3 properties 3 required
country-code
string
The country (in its ISO 3166 alpha-2 format) associated with this address.
payment-method-klarna
object
2 properties 2 required
profile-creation-data
credit-card-error
object
2 properties 2 required
cart-error
object
2 properties 2 required
three-ds-error
object
An error that occurs during 3D Secure authentication or verification.
2 properties 2 required
transaction
object
2 properties
amount
object
A monetary amount, i.e. a base unit amount and a supported currency.
2 properties 2 required
profile
object
An account's identifying information.
4 properties 3 required
payment-method-klarna-account
object
2 properties 2 required
payment-action-request
object
2 properties 1 required
cart-shipment
object
3 properties
payment-response
payment-method-extended
payment-method-applepay
address-reference-explicit
object
13 properties 7 required
address-reference-id
object
2 properties 2 required
credit-card-network
string
The credit card's network.
guest-payment-initialize-request
object
7 properties 3 required
error
object
2 properties 2 required
cart-item
object
9 properties 5 required
transaction-authorization
object
2 properties
payment-method-paypal
object
3 properties 3 required
payment-method
payment-method-credit-card

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bolt-payments-api-openapi.yml Raw ↑

Other APIs Bolt publishes across the network.

Bolt API
Embeddable Checkout v3 API
Merchant Callback API
Subscriptions API
Tokenizer API
Bolt Connect Merchant Onboarding API
Checkout Everywhere API
Bolt Account API
Bolt Callbacks API
Bolt OAuth API
Bolt Orders API
Bolt Testing API
Where this information came from

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