Auto-pagination

Our libraries support auto-pagination. This feature allows you to easily iterate through large lists of resources without having to manually perform the requests to fetch subsequent pages.

To use the auto-pagination feature in Node 10+, simply iterate over a “list” call with the parameters you need in a for await loop.

To use the auto-pagination feature in older versions of Node, issue a “list” call with the parameters you need, then call autoPagingEach(onItem) on the returned list object to iterate over all objects matching your initial parameters.

Full docs are on the stripe-node GitHub repository.

const Stripe = require('stripe');
const stripe = Stripe('sk_test_BQokikJ...2HlWgH4olfQ2sk_test_BQokikJOvBiI2HlWgH4olfQ2');
// In Node 10+:
for await (const customer of stripe.customers.list({limit: 3})) {
  // Do something with customer
}
// In other environments:
stripe.customers.list({limit: 3})
  .autoPagingEach(function(customer) {
    // Do something with customer
  });

Request IDs

Each API request has an associated request identifier. You can find this value in the response headers, under Request-Id. You can also find request identifiers in the URLs of individual request logs in your Dashboard.

To expedite the resolution process, provide the request identifier when you contact us about a specific request.

const Stripe = require('stripe');
const stripe = Stripe('sk_test_BQokikJ...2HlWgH4olfQ2sk_test_BQokikJOvBiI2HlWgH4olfQ2');
var customer = await stripe.customers.create();
console.log(customer.lastResponse.requestId);

Connected Accounts

If you use Stripe Connect, you can issue requests on behalf of your connected accounts. To act as a connected account, include a Stripe-Account header containing the connected account ID, which typically starts with the acct_ prefix.

The connected account ID is set per-request. Methods on the returned object reuse the same account ID.

Related guide: Making API calls for connected accounts

Per-Request Account

stripe.charges.retrieve('ch_3LmjSR2eZvKYlo2C1cPZxlbL', {
  stripeAccount: 'acct_1032D82eZvKYlo2C'
});

Versioning

Each major release, such as Acacia, includes changes that aren’t backward-compatible with previous releases. Upgrading to a new major release can require updates to existing code. Each monthly release includes only backward-compatible changes, and uses the same name as the last major release. You can safely upgrade to a new monthly release without breaking any existing code. The current version is 2025-12-15.clover. For information on all API versions, view our API changelog.

Starting from stripe-node v12, the requests you send using stripe-node align with the API version that was current when your version of stripe-node was released. This ensures that your TypeScript types are compatible with the API version you use.
On stripe-node v11 or lower, requests made with stripe-node use your Stripe account’s default API version (controlled in Workbench).

You can override the API version in your code in all versions.

To override the API version, provide the apiVersion option when initializing the library, or set it per-request. This might cause inaccurate Typescript types.

Webhook events also use your account’s API version by default, unless you set an API version during endpoint creation.

You can upgrade your API version in Workbench. As a precaution, use API versioning to test a new API version before committing to an upgrade.