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

Stripe Intents API

The Intents API from Stripe — 9 operation(s) for intents.

Stripe Intents API is one of 159 APIs that Stripe publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Intents. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and an AsyncAPI specification.

This API exposes 11 operations across 9 paths, and defines 15 schemas. It is described by OpenAPI 3.2.0, at version 2023-10-16.

Requests are made against a single base URL, https://api.stripe.com/.

11 operations 9 paths 15 schemas 3 GET8 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2023-10-16
Server
https://api.stripe.com/
Authentication
HTTP Basic, HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 2

Stripe Intents API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). It accepts HTTP bearer tokens (auth-scheme) (bearerAuth). By default, every request must be authenticated.

  • basicAuth — Basic HTTP authentication. Allowed headers-- Authorization: Basic | Authorization: Basic
  • bearerAuth — Bearer HTTP authentication. Allowed headers-- Authorization: Bearer

Paths & Operations 11

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

Intents 11
GET
/v1/payment_intents
Stripe Get Payment Intents
getPaymentIntents 6 params body → 200default
POST
/v1/payment_intents
Stripe Post Payment Intents
postPaymentIntents body → 200default
GET
/v1/payment_intents/search
Stripe Get Payment Intents Search
getPaymentIntentsSearch 4 params body → 200default
GET
/v1/payment_intents/{intent}
Stripe Get Payment Intents
getPaymentIntentsIntent 3 params body → 200default
POST
/v1/payment_intents/{intent}
Stripe Post Payment Intents
postPaymentIntentsIntent 1 param body → 200default
POST
/v1/payment_intents/{intent}/apply_customer_balance
Stripe Post Payment Intents Apply Customer Balance
postPaymentIntentsIntentApplyCustomerBalance 1 param body → 200default
POST
/v1/payment_intents/{intent}/cancel
Stripe Post Payment Intents Cancel
postPaymentIntentsIntentCancel 1 param body → 200default
POST
/v1/payment_intents/{intent}/capture
Stripe Post Payment Intents Capture
postPaymentIntentsIntentCapture 1 param body → 200default
POST
/v1/payment_intents/{intent}/confirm
Stripe Post Payment Intents Confirm
postPaymentIntentsIntentConfirm 1 param body → 200default
POST
/v1/payment_intents/{intent}/increment_authorization
Stripe Post Payment Intents Increment Authorization
postPaymentIntentsIntentIncrementAuthorization 1 param body → 200default
POST
/v1/payment_intents/{intent}/verify_microdeposits
Stripe Post Payment Intents Verify Microdeposits
postPaymentIntentsIntentVerifyMicrodeposits 1 param body → 200default

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are payment_intent (39 properties), PostPaymentIntentsRequest (31 properties), PostPaymentIntentsIntentRequest (20 properties), PostPaymentIntentsIntentConfirmRequest (17 properties). Each schema is shown below with its type and property counts.

PostPaymentIntentsIntentRequest
object
20 properties
SearchResult
object
6 properties 4 required
GetPaymentIntentsRequest
object
PaymentFlowsPaymentIntentList
object
4 properties 4 required
PostPaymentIntentsIntentConfirmRequest
object
17 properties
PostPaymentIntentsIntentCaptureRequest
object
8 properties
PostPaymentIntentsIntentCancelRequest
object
2 properties
PostPaymentIntentsIntentApplyCustomerBalanceRequest
object
3 properties
error
object
An error response from the Stripe API
1 property 1 required
PostPaymentIntentsIntentVerifyMicrodepositsRequest
object
4 properties
PostPaymentIntentsRequest
object
31 properties 2 required
PostPaymentIntentsIntentIncrementAuthorizationRequest
object
7 properties 1 required
GetPaymentIntentsIntentRequest
object
payment_intent
object
A PaymentIntent guides you through the process of collecting a payment from your customer. We recommend that you create exactly one PaymentIntent for each orde…
39 properties 10 required
GetPaymentIntentsSearchRequest
object

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

stripe-intents-api-openapi.yml Raw ↑

Other APIs Stripe publishes across the network.

Stripe Accounts API
Stripe Balance API
Stripe Billing API
Stripe Charges API
Stripe Checkout API
Stripe Climate API
Stripe Country API
Stripe Coupons API
Stripe Credit Notes API
Stripe Customers API
Stripe Disputes API
Stripe Ephemeral Keys API
Where this information came from

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