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

The Configurations API from Stripe — 4 operation(s) for configurations.

Stripe Configurations 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 Configurations. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and an AsyncAPI specification.

This API exposes 8 operations across 4 paths, and defines 13 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/.

8 operations 4 paths 13 schemas 4 GET4 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 Configurations 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 8

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

Configurations 8
GET
/v1/billing_portal/configurations
Stripe Get Billing Portal Configurations
getBillingPortalConfigurations 6 params body → 200default
POST
/v1/billing_portal/configurations
Stripe Post Billing Portal Configurations
postBillingPortalConfigurations body → 200default
GET
/v1/billing_portal/configurations/{configuration}
Stripe Get Billing Portal Configurations Configuration
getBillingPortalConfigurationsConfiguration 2 params body → 200default
POST
/v1/billing_portal/configurations/{configuration}
Stripe Post Billing Portal Configurations Configuration
postBillingPortalConfigurationsConfiguration 1 param body → 200default
GET
/v1/payment_method_configurations
Stripe Get Payment Method Configurations
getPaymentMethodConfigurations 2 params body → 200default
POST
/v1/payment_method_configurations
Stripe Post Payment Method Configurations
postPaymentMethodConfigurations body → 200default
GET
/v1/payment_method_configurations/{configuration}
Stripe Get Payment Method Configurations
getPaymentMethodConfigurationsConfiguration 2 params body → 200default
POST
/v1/payment_method_configurations/{configuration}
Stripe Post Payment Method Configurations
postPaymentMethodConfigurationsConfiguration 1 param body → 200default

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are payment_method_configuration (41 properties), PostPaymentMethodConfigurationsConfigurationRequest (37 properties), PostPaymentMethodConfigurationsRequest (37 properties), billing_portal.configuration (13 properties). Each schema is shown below with its type and property counts.

billing_portal.configuration
object
A portal configuration describes the functionality and behavior of a portal session.
13 properties 10 required
GetBillingPortalConfigurationsRequest
object
GetPaymentMethodConfigurationsConfigurationRequest
object
PortalPublicResourceConfigurationList
object
4 properties 4 required
error
object
An error response from the Stripe API
1 property 1 required
GetPaymentMethodConfigurationsRequest
object
PostBillingPortalConfigurationsRequest
object
6 properties 2 required
PaymentMethodConfigResourcePaymentMethodConfigurationsList
object
4 properties 4 required
PostPaymentMethodConfigurationsRequest
object
37 properties
PostBillingPortalConfigurationsConfigurationRequest
object
7 properties
PostPaymentMethodConfigurationsConfigurationRequest
object
37 properties
payment_method_configuration
object
PaymentMethodConfigurations control which payment methods are displayed to your customers when you don't explicitly specify payment method types. You can have…
41 properties 6 required
GetBillingPortalConfigurationsConfigurationRequest
object

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

stripe-configurations-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 Configurations 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.