Setting the chapter. One moment.
Skills
Chapter 7 of 7
Guide for upgrading Stripe API versions and SDKs
3 minutes · 576 words · 18 sections
The latest Stripe API version is 2026-07-29.dahlia - use this version when upgrading unless the user specifies a different target version.
This guide covers upgrading Stripe API versions, server-side SDKs, Stripe.js, and mobile SDKs.
Stripe uses date-based API versions (e.g., 2026-07-29.dahlia, 2025-08-27.basil, 2024-12-18.acacia). Your account’s API version determines request/response behavior.
Backward-Compatible Changes (don’t require code updates):
Breaking Changes (require code updates):
Review the API Changelog (opens in a new tab) for all changes between versions.
See SDK Version Management (opens in a new tab) for details.
These SDKs offer flexible version control:
Global Configuration:
import stripe
stripe.api_version = '2026-07-29.dahlia'Stripe.api_version = '2026-07-29.dahlia'const stripe = require('stripe')('sk_test_xxx', {
apiVersion: '2026-07-29.dahlia'
});Per-Request Override:
stripe.Customer.create(
email="customer@example.com",
stripe_version='2026-07-29.dahlia'
)These use a fixed API version matching the SDK release date. Don’t set a different API version for strongly-typed languages because response objects might not match the strong types in the SDK. Instead, update the SDK to target a new API version.
Always specify the API version you’re integrating against in your code instead of relying on your account’s default API version:
// Good: Explicit version
const stripe = require('stripe')('sk_test_xxx', {
apiVersion: '2026-07-29.dahlia'
});
// Avoid: Relying on account default
const stripe = require('stripe')('sk_test_xxx');See Stripe.js Versioning (opens in a new tab) for details.
Stripe.js uses an evergreen model with major releases (Acacia, Basil, Clover, Dahlia) on a biannual basis.
Via Script Tag:
<script src="https://js.stripe.com/dahlia/stripe.js"></script>Via npm:
npm install @stripe/stripe-jsMajor npm versions correspond to specific Stripe.js versions.
Each Stripe.js version automatically pairs with its corresponding API version. For instance:
2026-07-29.dahlia API2024-12-18.acacia APIYou can’t override this association.
See Mobile SDK Versioning (opens in a new tab) for details.
Both platforms follow semantic versioning (MAJOR.MINOR.PATCH):
New features and fixes release only on the latest major version. Upgrade regularly to access improvements.
Uses a different model (0.x.y schema):
All mobile SDKs work with any Stripe API version you use on your backend unless documentation specifies otherwise.
npm update stripe, pip install --upgrade stripe)apiVersion parameter in your Stripe client initializationStripe-Version headerUse the Stripe-Version header to test your code against a new version without changing your default:
curl https://api.stripe.com/v1/customers \
-u sk_test_xxx: \
-H "Stripe-Version: 2026-07-29.dahlia"Or in code:
const stripe = require('stripe')('sk_test_xxx', {
apiVersion: '2026-07-29.dahlia' // Test with new version
});Install this repository
npx skills add stripe/ai/plugin marketplace add stripe/aiSkills install per repository, not per chapter — the CLI has no documented per-skill form, so we do not print one.
skills/upgrade-stripe/SKILL.mdmain, last pushed 8 August 2026.SKILL.md, not by matching a directory convention. One layout observed: skills/*/SKILL.md.h1 and no skipped levels:.claude-plugin/marketplace.json by Stripe, declaring 1 plugin. It is read for editorial metadata only — never as the skill index, which is always the repository tree./stripe/ai.md, and each chapter at its own .md URL.