Skip to content

docs: add warning about source-stripe-native's events API version#3166

Merged
nicolaslazo merged 1 commit into
masterfrom
lazo/docs-stripe-native-events-api-version-warning
Jul 17, 2026
Merged

docs: add warning about source-stripe-native's events API version#3166
nicolaslazo merged 1 commit into
masterfrom
lazo/docs-stripe-native-events-api-version-warning

Conversation

@nicolaslazo

Copy link
Copy Markdown
Contributor

Description:

Documents an observed exception in the Stripe API: the events endpoint does not respect API version overrides.

Workflow steps:

(How does one use this feature, and how has it changed)

Documentation links affected:

(list any documentation links that you created, or existing ones that you've identified as needing updates, along with a brief description)

Notes for reviewers:

(anything that might help someone review this PR)

@nicolaslazo nicolaslazo self-assigned this Jul 14, 2026
@nicolaslazo
nicolaslazo requested a review from a team July 14, 2026 17:53
@github-actions

Copy link
Copy Markdown

Alex-Bair
Alex-Bair previously approved these changes Jul 14, 2026

@Alex-Bair Alex-Bair left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -31,6 +27,10 @@ The connector handles several known limitations of the Stripe API:
- **Connected account child streams**: Resources like Persons, ExternalAccountCards, and ExternalBankAccount must be queried through parent account endpoints (e.g., `/v1/accounts/{id}/persons`), requiring per-account queries when capturing connected accounts.
- **Events API retention**: Stripe retains events for 30 days. While other resources can backfill beyond this window using their own list endpoints, the Events stream is limited to the most recent 30 days regardless of the configured `start_date`. The connector gracefully handles this by treating Stripe's retention expiry as a completed backfill.

:::warning
The **API Version** advanced configuration field does not apply to the Events stream. Because Stripe fixes an event's `api_version` at creation time and does not re-render events at a requested version, events are always captured in the version under which they were originally generated.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The **API Version** advanced configuration field does not apply to the Events stream. Because Stripe fixes an event's `api_version` at creation time and does not re-render events at a requested version, events are always captured in the version under which they were originally generated.
The **API Version** advanced configuration field does not apply to the Events stream or streams that incrementally capture changes based off the `/events` endpoint. Because Stripe fixes an event's `api_version` at creation time and does not re-render the event's `data` object at a requested version, events and objects incrementally captured based on events are always captured in the version under which they were originally generated.

It may also help to link to Stripe's API docs stating this behavior too.

@nicolaslazo
nicolaslazo force-pushed the lazo/docs-stripe-native-events-api-version-warning branch from 1b51fda to 745eda1 Compare July 17, 2026 13:38
@nicolaslazo
nicolaslazo requested a review from Alex-Bair July 17, 2026 13:38
@nicolaslazo
nicolaslazo merged commit 6ec51cb into master Jul 17, 2026
8 checks passed
@nicolaslazo
nicolaslazo deleted the lazo/docs-stripe-native-events-api-version-warning branch July 17, 2026 13:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants