Stripe API
Public
Stripe's official OpenAPI 3.0 specification for its payments and billing API, published by Stripe under the MIT license.
Use Cases
Agent Grounding
FinanceAI agents look up exact Stripe object fields, such as how an invoice line links to a subscription and a customer, instead of guessing them when writing code or SQL.
Webhook Payload Validation
Tech / ITPlatform teams validate incoming Stripe event payloads against the event and resource schemas before processing them.
Payment Integration Development
Tech / ITDevelopers generate typed clients or validate request and response payloads for PaymentIntent, Checkout Session and Refund calls against the published component schemas.
Revenue Analytics Modeling
FinanceData engineers model Stripe sources such as customer, invoice, subscription and balance_transaction before building dbt staging and revenue models, using the resource shapes to plan joins and tests. The Fivetran package fivetran/stripe covers the common billing tables.
Overview
The Stripe API specification describes the objects and operations of Stripe's payments platform as an OpenAPI 3.0 document. Stripe publishes it in the stripe/openapi repository and updates it with each API release; release 2026-09-30.endive defines 1,538 component schemas and 431 paths. Its core resources cover the payment lifecycle (PaymentIntent, Charge, Refund, Dispute), billing (Customer, Product, Price, Subscription, Invoice), money movement (Balance Transaction, Payout) and hosted flows (Checkout Session). Expandable fields name the resources they expand to, which makes object relationships explicit. The library copy holds 1,307 types imported from an earlier release of the same specification. Data engineers can use it to model Stripe sources before writing dbt staging models, and agents can query it to ground payment and billing tasks in Stripe's actual object shapes.
Top entities
customer, charge, payment_intent, invoice, subscription, price, product, refund, payout, balance_transaction, dispute, checkout.session
Mappings
- Fivetran dbt package fivetran/stripe: partial. Staging and transformation models cover the main billing and balance objects.
- schema.org Invoice and Order: conceptual. Invoice and checkout objects align in intent, not field by field.
- Open Semantic Interchange (OSI) revenue metrics: conceptual. Balance transactions and invoices are common inputs to revenue metric definitions.
For agents
Query the library's CoreModels project for resource shapes before generating code or SQL against Stripe data. Sample prompt: "Using the Stripe API schema in the Schematica Library, list the fields of invoice and subscription that link a line item to its customer." Read via MCP: get_project_summary with graphProjectId 739766df48d94da78d6bf8a417db4982.
Provenance
Publisher: Stripe. License: MIT (https://github.com/stripe/openapi). Version: 2026-09-30.endive. Format: OpenAPI 3.0 (listed here as JSON Schema until the library format list includes OpenAPI). Described by the Schema Librarian on 2026-10-22; auto-cataloged.
Comments: