Setting the skill. One moment.
Skills
Skill 10 of 10
Guide for upgrading Stripe API versions, webhook endpoints, server-side SDKs, Stripe.js, and mobile SDKs
4 minutes · 988 words · 19 sections
Install
npx skills add stripe/ai --skill upgrade-stripenpx skills add stripe/ai/plugin marketplace add stripe/aiThe first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.
If the user specifies a target API version, use it. Otherwise, look up the current version on docs.stripe.com with any documentation or web tool available to you, for example stripe docs /api/versioning with the Stripe CLI. The API versioning (opens in a new tab) page states it in the sentence that begins “The current version is”.
Bundled fallback API version: 2026-08-26.dahlia. This value is only a snapshot from the last time this skill was generated, on 2026-09-24. Version identifiers start with their release date in YYYY-MM-DD format and new stable versions are released monthly, so a fallback version dated more than a month ago is probably stale. Use it only when you can’t reach docs.stripe.com. Never guess about a newer version number.
Before making changes, compare the target with each API version the integration pins: client configuration, per-request overrides, and webhook endpoints. Unless the user explicitly asks for it, don’t move any pin to an older version or a stable pin to a preview version. If a pin already matches the target, report it as unchanged. State the selected target and its source. If live verification fails or is unavailable, say that the latest version remains unverified, and don’t claim the integration is on the latest version.
When reviewing webhook endpoints and event destinations, distinguish snapshot events from thin events. Thin event payloads are unversioned, so they don’t need to be upgraded when you change your API version. API calls that retrieve the full event or related resource remain versioned.
For SDKs that support explicit API version overrides, use the selected target in client configuration and per-request overrides. Use it in curl Stripe-Version test headers, too. Replace bundled API versions shown in those examples with the selected target before copying or running them. For Java, Go, and .NET, select an SDK release that targets the selected API version instead of overriding the SDK’s fixed version. Preview targets need the matching beta SDK release in every language; see SDK versioning (opens in a new tab).
Stripe uses date-based API versions (e.g., 2026-08-26.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-08-26.dahlia'Stripe.api_version = '2026-08-26.dahlia'const stripe = require('stripe')('sk_test_xxx', {
apiVersion: '2026-08-26.dahlia'
});Per-Request Override:
stripe.Customer.create(
email="customer@example.com",
stripe_version='2026-08-26.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-08-26.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-08-26.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-08-26.dahlia"Or in code:
const stripe = require('stripe')('sk_test_xxx', {
apiVersion: '2026-08-26.dahlia' // Test with new version
});skills/upgrade-stripe/SKILL.mdmain, last pushed 24 September 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 skill at its own .md URL.