Stripe
Use this page to set up the Stripe source connector and find reference information.
Prerequisites
- Access to the Stripe account containing the data you want to replicate
- Stripe Account ID
Setup
:::note You need a Stripe API key to authenticate the Stripe connector. You can use an existing key. However, it’s best to create a restricted key specifically for Airbyte and grant only Read privileges. Grant Read privileges to all available permissions. Then configure the specific data you want to replicate within Airbyte. :::
1. Set up Stripe
- Log in to your Stripe account.
- In the top navigation bar, click Developers.
- In the top-left corner, click API keys.
- Click + Create restricted key.
- Choose a Key name, then select Read for all available permissions.
- Click Create key. You may need to enter a confirmation code sent to your email address.
For more information about Stripe API Keys, see the Stripe documentation.
2. Set up the Stripe connector in Airbyte
For Airbyte Cloud:
- Log into your Airbyte Cloud account.
- Click Sources, then click + New source.
- On the Set up the source page, select Stripe from the Source type dropdown.
- Enter a name for the Stripe connector.
Airbyte Open Source
- Go to the Airbyte Open Source dashboard.
- Click Sources, then click + New source.
- On the Set up the source page, select Stripe from the Source type dropdown.
- Enter a name for the Stripe connector.
-
For Account ID, enter your Stripe Account ID. This ID begins with
acct_. Find it in the top-right corner of your Stripe account settings page. -
For Secret Key, enter the restricted key you created for the connection.
-
For Replication Start Date, use the datepicker or enter a UTC date and time programmatically in the format
YYYY-MM-DDTHH:mm:ssZ. Data added on or after this date will be replicated. -
(Optional) For Lookback Window, specify how many days of data to reread from the present day. This retrieves data that may have changed after its initial creation. It’s useful for handling post-transaction adjustments. This applies only to streams without event-based incremental syncs. See the list below.
- Keep Lookback Window at its default value of 0 to prevent Airbyte re-exporting data after it syncs.
- Set Lookback Window to 1 to re-export data from the past day. This captures changes from the last 24 hours.
- Set Lookback Window to 7 to re-export and capture data changes from the last week.
-
(Optional) For Data Request Window, specify the time window, in days, for Stripe API data requests. This window sets the period covered by each request. Larger values include more days in one request. Fewer requests generally reduce overhead, so a larger window syncs faster. However, the sync state then persists less often. If the sync fails or stops, more data must be resynced. This may delay the overall process.
For example, if you’re replicating three years of data:
- A Data Request Window of 365 days makes 3 requests, each covering one year. This is generally faster. However, an interrupted sync may need to resync up to one year of data.
- A Data Request Window of 30 days makes 36 requests, each covering one month. This may be slower. However, less data needs resyncing if a problem occurs.
If you’re unsure which value to use, keep the default setting of 365 days.
-
(Optional) For Streams with API Data Retention Validation, select streams whose cursor age should be checked against Stripe’s 30-day Events API retention limit. If a selected stream’s cursor is older than 30 days, the connector runs a full refresh. This replaces an incremental sync that would miss older changes. By default, no streams are selected. The connector therefore never overrides a stream’s configured sync mode based on cursor age. For guidance on which streams benefit from this check, see Cursor age validation and automatic full refresh.
-
(Optional) For Accounts start date, enter when the
Accountsstream should start reading connected accounts. Use a UTC date and time in the formatYYYY-MM-DDTHH:mm:ssZ. The default,2010-01-01T00:00:00Z, reads every connected account. A later date excludes accounts created before it, including during full refreshes.Personsreads its accounts from theAccountsstream. The persons belonging to excluded accounts are therefore also excluded. -
(Optional) For Number of Concurrent Threads, enter the number of worker threads for the sync. The default is 10. You can enter any value from 2 to 100. Higher values increase throughput and API usage. Your Stripe account’s rate limits determine the effective upper limit.
-
(Optional) For Max Number of API Calls per Second, enter the connector’s maximum number of API requests per second. By default, it makes 25 calls per second with test and sandbox API keys. It makes 100 calls per second with live API keys. This value can’t exceed Stripe’s actual rate limits.
-
Click Set up source and wait for the tests to finish.
Supported sync modes
The Stripe source connector supports these sync modes:
- Full Refresh
- Incremental
Supported streams
The Stripe source connector supports these streams:
- Accounts (Incremental)
- Application Fees (Incremental)
- Application Fee Refunds (Incremental)
- Authorizations (Incremental)
- Balance Transactions (Incremental)
- Bank accounts (Incremental)
- Cardholders (Incremental)
- Cards (Incremental)
- Charges (Incremental)
:::note
The
amountcolumn defaults to the smallest currency unit. See the Stripe docs for details. ::: - Checkout Sessions (Incremental)
- Checkout Sessions Line Items (Incremental)
- Coupons (Incremental)
- Credit Notes (Incremental)
- Customer Balance Transactions (Incremental)
- Customers (Incremental)
- Disputes (Incremental)
- Early Fraud Warnings (Incremental)
- Events (Incremental)
- External Account Bank Accounts (Incremental)
- External Account Cards (Incremental)
- File Links (Incremental)
- Files (Incremental)
- Invoice Items (Incremental)
- Invoice Line Items (Incremental)
:::note
During incremental syncs, this stream reads line items from the invoice object embedded in
invoice.created,invoice.updated, andinvoice.deletedevents. Stripe embeds up to 10 line items in that payload. For larger invoices, the connector requests the remaining items from/v1/invoices/{invoice_id}/lines. This ensures every invoice has complete line items. Before version 6.0.19, incremental syncs kept only the first 10 line items from each invoice. If an earlier version synced larger invoices, run a full refresh of this stream to repair the existing data. ::: - Invoices (Incremental)
- Payment Intents (Incremental)
- Payment Methods (Incremental)
- Payouts (Incremental)
- Payout Balance Transactions (Incremental) :::note This stream calls the balance transaction API using payout_id from the parent payout stream. This returns the balance transactions that make up the payout’s actual amount. See the Stripe docs for details. :::
- Promotion Codes (Incremental)
- Persons (Incremental)
- Plans (Incremental)
- Prices (Incremental)
- Products (Incremental)
- Refunds (Incremental)
- Reviews (Incremental)
- Setup Attempts (Incremental)
- Setup Intents (Incremental)
- Shipping Rates (Incremental)
- Subscription Items (Incremental)
- Subscription Schedule (Incremental)
- Subscriptions (Incremental)
- Top Ups (Incremental)
- Transactions (Incremental)
- Transfers (Incremental)
- Transfer Reversals (Incremental)
- Usage Records
Entity-relationship diagram
Data type map
The Stripe API uses the same JSON Schema types as Airbyte: (string, date-time, object, array, boolean, integer, and number). The Stripe connector therefore performs no type conversions.
Stripe API version
This connector sends Stripe API version 2022-11-15 with every request. Objects read directly from Stripe endpoints follow this version. This applies to full refresh syncs and each stream’s first sync. Your Stripe dashboard’s configured version doesn’t affect their shape.
Incremental syncs work differently for streams that read from the Events API. Stripe renders each event’s data.object using the account’s default API version when the event was created. The connector’s requested version doesn’t change it. Incremental event records can therefore differ from full refresh records. For example, fields changed in later API versions may be missing or null. For details, see Stripe API upgrades and Versioning.
Limitations and troubleshooting
Expand to see details about Stripe connector limitations and troubleshooting.
Connector limitations
Rate limits
The Stripe connector automatically handles API rate limits. This includes retries and backoff for HTTP 429 responses. Stripe enforces a limit of 25 requests per second for sandbox keys and 100 requests per second for live keys. The connector follows these limits and adjusts its request rate.
If you encounter rate limits, reduce the Number of concurrent threads setting in the connector configuration. The default is 10 for live keys and 4 for sandbox keys. You can also configure a Max number of API calls per second to set a stricter limit. Create an issue if rate-limit retries don’t succeed automatically.
:::warning
Stripe API Restriction on Events Data: Stripe guaranteed only for the last 30 days access to the events endpoint. With Full Refresh Overwrite, events data older than 30 days will be deleted from your target destination. Only data from the last 30 days will replace it. Use Append sync mode to retain historical data.
Streams using the updated cursor rely on the Events API and have the same limit. Incremental sync can’t replicate a change older than 30 days. Sync at least once every 30 days to keep these streams current.
:::
Validate cursor age
The connector can validate each stream’s cursor age to prevent data loss from the Events API’s 30-day retention limit. It does this before choosing an incremental or full refresh sync. If a cursor is older than 30 days, the connector runs a full refresh for that stream. Otherwise, the Events API would return only the last 30 days of data.
This behavior is configurable via the “Streams with API Data Retention Validation” setting (see setup guide step 10). The connector validates cursor age only for streams listed in this setting. By default, no streams are selected. All streams therefore use incremental sync without cursor age validation.
Cursor age validation is recommended for high-usage streams such as Charges, Invoice Items, Invoice Line Items, Invoices, Payment Intents, and Payouts. For these streams, a stale cursor probably indicates missing data rather than normal inactivity. Streams such as Customers, Subscriptions, Products, and Plans may not need validation. Some accounts legitimately have no new records for over 30 days, making a full refresh unnecessary.
To choose which streams use cursor age validation, change the Streams with API Data Retention Validation list in your connection settings. These streams are eligible:
Application FeesApplication Fee RefundsAuthorizationsBank AccountsCardholdersChargesCheckout SessionsCouponsCredit NotesCustomersDisputesEarly Fraud WarningsExternal Account Bank AccountsExternal Account CardsInvoice ItemsInvoice Line ItemsInvoicesPayment IntentsPayment MethodsPayoutsPersonsPlansPricesProductsPromotion CodesRefundsReviewsSetup IntentsSubscription ItemsSubscription ScheduleSubscriptionsTop UpsTransactionsTransfers
Accounts remains in the Streams with API Data Retention Validation setting to keep saved configurations valid. However, selecting it has no effect. Since version 7.1.0, the Accounts stream hasn’t read the Events API. It therefore has no 30-day retention limit to check.
:::warning Important: If you remove a stream from the validation list, the connector still uses incremental sync when its cursor becomes stale. The Events API returns only the last 30 days of data. You may therefore miss updates to records older than 30 days. Remove a stream only when a stale cursor is acceptable for your use case. :::
Troubleshooting
The Stripe API can’t query objects updated since the last sync. The Stripe connector therefore uses the Events API for incremental syncs and exports data by update date.
The Events API doesn’t support every entity. For unsupported entities, the connector queries new Stripe data using the created field or its equivalent. These entities sync by creation date:
Accounts(cursor field isupdated, set fromcreated)Balance TransactionsCustomer Balance TransactionsEventsFile LinksFilesSetup AttemptsShipping RatesTransfer Reversals
The following streams instead use the updated field value as their cursor:
:::note
Airbyte adds updated as an artificial cursor field for incremental sync. Stripe doesn’t return it.
For records rebuilt from the Events API, updated comes from the event timestamp. Stripe records this timestamp with one-second resolution. Records derived from a *.created event receive a cursor one second before the event. This offset breaks ties when creation and update events for the same object occur within one second. The update sorts higher, so deduplicating destinations retain its payload instead of the older creation payload.
:::
Application FeesApplication Fee RefundsAuthorizationsBank AccountsCardholdersCardsChargesCheckout SessionsCheckout Session Line Items(cursor field ischeckout_session_updated)CouponsCredit NotesCustomersDisputesEarly Fraud WarningsExternal Account Bank AccountsExternal Account CardsInvoice ItemsInvoice Line Items(cursor field isinvoice_updated)InvoicesPayment IntentsPayment MethodsPayoutsPayout Balance TransactionsPromotion CodesPersonsPlansPricesProductsRefundsReviewsSetup IntentsSubscription ScheduleSubscription Items(cursor field issubscription_updated)SubscriptionsTop UpsTransactionsTransfers
Connected accounts sync only when created
The Accounts stream lists a Stripe Connect platform’s connected accounts. Incremental syncs read /v1/accounts filtered by created. New connected accounts therefore arrive during the next sync. Changes to existing connected accounts aren’t detected, including changes to charges_enabled or requirements. Stripe places account.updated events in each connected account’s event feed, not the platform’s feed. The connector therefore can’t detect those changes through the Events API. Refresh the Accounts stream when you need current details for existing connected accounts.
The Persons stream has the same limitation. Its incremental syncs read only person.* events. Stripe’s Connect webhooks page lists person.created, person.updated and person.deleted among events delivered for connected accounts. New and changed persons may therefore not arrive until you refresh the stream. It reads parent accounts from the Accounts start date using the same created windows as the Accounts stream.
Since version 7.1.0:
- A full refresh reads
/v1/accountsin 30-daycreatedwindows. These run from the Accounts start date, January 2010 by default, to now. It reads up to Number of Concurrent Threads windows concurrently. Stripe permits 50 in-progress requests per live-mode account, shared across all streams. See Stripe’s rate limits. Values above about 25 offer little benefit and can trigger rate-limit retries. - A full refresh saves its bookmark only after the entire read finishes. After a failed attempt, the retry starts from the first window instead of resuming.
- After a full read, the stream stores its bookmark in the format
Bank Accountshas used since 7.0.3. Earlier connector versions read it without errors. - Stripe doesn’t return
createdfor Standard connected accounts. Theirupdatedvalue is the sync time, as in earlier versions. - The
Personsstream reads its parent accounts one window at a time. It therefore gains no speed from this change. - After upgrading, the first incremental sync continues from the saved bookmark minus the Lookback Window. The bookmark usually records your last full read’s time. New connected accounts therefore arrive from that point, but changes to existing accounts aren’t detected. Refresh the
Accountsstream once after upgrading if you need every connected account or those changes.
Invoice line item IDs without il_
Stripe accounts using a default API version older than 2019-12-03 receive legacy invoice line item IDs in events. These include ii_..., item_..., sub_..., su_..., or sli_.... Before version 7.0.0, incremental invoice_line_items syncs could write these legacy IDs. Full refresh syncs wrote the current il_... IDs for the same line items. A sub_... or su_... ID belongs to the subscription, so it repeats across renewal invoices. A deduplicated destination therefore retained only the most recent of those lines.
From version 7.0.0, incremental syncs write il_... IDs. Rows from earlier versions aren’t removed automatically. Until you remove them, affected line items can appear twice: under the legacy ID and the il_... ID. To check whether you’re affected, run a query like this against your destination:
SELECT COUNT(*) FROM <your_schema>.invoice_line_items WHERE SUBSTR(id, 1, 3) <> 'il_';
If the count exceeds zero, upgrade to 7.0.0 or later, then refresh the invoice_line_items stream and remove records. Refreshing and removing records deletes this stream’s existing destination data, including rows Stripe can’t resend. The refreshed stream rebuilds from the Invoices endpoints, not the 30-day Events API window. However, it includes only invoices created on or after your configured start date. It doesn’t recreate line items from invoices created before that date. It also excludes deleted draft invoice rows where is_deleted is true. In an Incremental | Append destination, it doesn’t recreate earlier versions of each line item. Back up the invoice_line_items table before refreshing if you need these rows or legacy IDs. Refreshing while retaining records doesn’t remove legacy rows because they use a different primary key. For details, see the 7.0.0 migration guide.
Incremental deletes
The Stripe API supports incremental deletes for these streams:
Bank AccountsCouponsCustomersExternal Account Bank AccountsExternal Account CardsInvoicesInvoice ItemsPersonsPlansPricesProductsSubscriptions
The appropriate upstream event marks each record with the is_deleted flag.
- Find common troubleshooting issues for the Stripe source connector on the Airbyte Forum.
IP allow list
If you use Airbyte Cloud and restrict access to specific IPs, add the Airbyte Cloud IP addresses to your allow list.
Changelog
Expand to review
| Version | Date | Pull Request | Subject |
|---|---|---|---|
| 7.1.0 | 2026-11-03 | 90436 | Read accounts from /v1/accounts by created: incremental syncs pick up new connected accounts, full refreshes read parallel 30-day windows |
| 7.0.7 | 2026-11-10 | 91749 | Update dependencies |
| 7.0.6 | 2026-11-03 | 90261 | Make interrupted customer_balance_transactions backfills resumable; fail on 400/403 for that stream instead of silently skipping customers |
| 7.0.5 | 2026-11-01 | 90396 | Simplify HTTP error handling configuration with no change to which errors are skipped or fail the sync |
| 7.0.4 | 2026-11-03 | 90764 | Update dependencies |
| 7.0.3 | 2026-10-20 | 89581 | Read bank_accounts full refreshes from 30-day customers slices instead of one partition per customer, and fail on HTTP 400 instead of silently skipping a slice |
| 7.0.2 | 2026-10-20 | 89447 | Update dependencies |
| 7.0.1 | 2026-10-13 | 88397 | Opt in to TCP keepalive and request timeouts (30 s connect, 80 s read) so dropped connections fail and retry instead of hanging |
| 7.0.0 | 2026-10-13 | 87765 | Use Stripe’s current il_ line item IDs for invoice_line_items on incremental syncs. See the migration guide. |
| 6.0.23 | 2026-10-13 | 88809 | Update dependencies |
| 6.0.22 | 2026-10-06 | 88070 | Update dependencies |
| 6.0.21 | 2026-09-29 | 87375 | Update dependencies |
| 6.0.20 | 2026-09-22 | 86838 | Update dependencies |
| 6.0.19 | 2026-09-21 | 85087 | Fix truncated invoice_line_items on incremental syncs: fetch the complete line item list from invoices/{id}/lines when the event payload embeds only the first page. Existing destination data for invoices with more than 10 line items requires a Full Refresh to repair. |
| 6.0.18 | 2026-09-15 | 86254 | Update dependencies |
| 6.0.17 | 2026-09-11 | 85799 | Prevent the events-based invoice_line_items and subscription_items transformations from running when original_record is missing or empty. |
| 6.0.16 | 2026-09-08 | 85672 | Update dependencies |
| 6.0.15 | 2026-08-18 | 84768 | Update dependencies |
| 6.0.14 | 2026-08-17 | 84355 | Update events now win same-second cursor ties with creation events so the newer payload is kept at the destination. |
| 6.0.13 | 2026-08-11 | 84134 | Update dependencies |
| 6.0.12 | 2026-08-04 | 83634 | Update dependencies |
| 6.0.11 | 2026-07-28 | 83119 | Update dependencies |
| 6.0.10 | 2026-07-21 | 82611 | Update dependencies |
| 6.0.9 | 2026-07-14 | 82034 | Update dependencies |
| 6.0.8 | 2026-06-30 | 81285 | Update dependencies |
| 6.0.7 | 2026-06-23 | 80686 | Update dependencies |
| 6.0.6 | 2026-06-16 | 80070 | Update dependencies |
| 6.0.5 | 2026-06-09 | 79523 | Update dependencies |
| 6.0.4 | 2026-06-03 | 79042 | Update dependencies |
| 6.0.3 | 2026-04-28 | 77424 | Update dependencies |
| 6.0.2 | 2026-04-21 | 76777 | Update dependencies |
| 6.0.1 | 2026-04-13 | 76276 | Rename “concurrent workers” to “concurrent threads” in connector spec |
| 6.0.0 | 2026-04-13 | 76095 | Fix missing records in invoice_line_items and subscription_items incremental streams by replacing DpathFlattenFields with RecordExpander to correctly expand nested line items from Stripe events. This is a breaking change — previously synced data for these streams may be incomplete. See the migration guide for details. |
| 5.15.23 | 2026-03-31 | 75864 | Update dependencies |
| 5.15.22 | 2026-03-12 | 74770 | Upgrade CDK to 7.13.0 |
| 5.15.21 | 2026-03-06 | 74342 | Promoting release candidate 5.15.21-rc.5 to a main version. |
| 5.15.21-rc.5 | 2026-03-06 | 74337 | Make API data retention validation optional per stream via new api_retention_streams config field, upgrade CDK to 7.8.1.post54 |
| 5.15.21-rc.4 | 2026-03-04 | 74290 | Lower default concurrency from 25 to 10 and increase default data request time increment from 30 to 365 days to reduce rate limiting |
| 5.15.21-rc.3 | 2026-03-03 | 74259 | Fix cursor age validation to clear state before constructing full refresh stream, ensuring true full refresh from start_date |
| 5.15.21-rc.2 | 2026-02-25 | 74051 | Fix sync failure when unselected parent streams have stale cursor state during cursor age validation |
| 5.15.21-rc.1 | 2026-02-25 | 73646 | Add cursor age validation for StateDelegatingStream streams to prevent data loss when initial sync fails mid-way |
| 5.15.20 | 2026-02-24 | 73944 | Update dependencies |
| 5.15.19 | 2026-02-17 | 73466 | Update dependencies |
| 5.15.18 | 2026-02-12 | 73318 | Promoting release candidate 5.15.18-rc.1 to a main version. |
| 5.15.18-rc.1 | 2026-02-04 | 72432 | fix(source-stripe): Fix Missing ConcurrencyLevel & Reduce Default Step Size |
| 5.15.17 | 2026-01-27 | 72363 | fix(source-stripe): Add date filtering for checkout_sessions full refresh |
| 5.15.16 | 2026-01-20 | 72106 | Update dependencies |
| 5.15.15 | 2026-01-14 | 71614 | Update dependencies |
| 5.15.14 | 2025-12-18 | 70638 | Update dependencies |
| 5.15.13 | 2025-11-25 | 70048 | Update dependencies |
| 5.15.12 | 2025-11-18 | 69580 | Update dependencies |
| 5.15.11 | 2025-10-29 | 68994 | Update dependencies |
| 5.15.10 | 2025-10-21 | 68527 | Update dependencies |
| 5.15.9 | 2025-10-14 | 67472 | Update dependencies |
| 5.15.8 | 2025-09-30 | 66891 | Update dependencies |
| 5.15.7 | 2025-09-24 | 66367 | Update dependencies |
| 5.15.6 | 2025-09-09 | 66115 | Update dependencies |
| 5.15.5 | 2025-08-24 | 65489 | Update dependencies |
| 5.15.4 | 2025-08-10 | 64840 | Update dependencies |
| 5.15.3 | 2025-08-04 | 64484 | Fix memory issue by moving schema loaders out of $parameters |
| 5.15.2 | 2025-08-03 | 64439 | Update dependencies |
| 5.15.1 | 2025-07-26 | 60561 | Update dependencies |
| 5.15.0 | 2025-07-23 | 63743 | Promoting release candidate 5.15.0-rc.1 to a main version. |
| 5.15.0-rc.1 | 2025-07-21 | 63370 | Migrate to manifest-only format. |
| 5.14.1 | 2025-07-15 | 62893 | Increase the timeout for syncs that fail without any records to one day. |
| 5.14.0 | 2025-07-15 | 63303 | Promoting release candidate 5.14.0-rc.1 to a main version. |
| 5.14.0-rc.1 | 2025-06-12 | 60846 | Rollback Low Code per partition streams; update slicer for invoice_line_items and normalization for events based streams |
| 5.13.0 | 2025-05-22 | 60846 | Update subscription_items and usage_records stream to python implementation |
| 5.12.0 | 2025-05-12 | 59743 | Update invoice_line_items stream to python implementation |
| 5.11.3 | 2025-05-10 | 60053 | Update dependencies |
| 5.11.2 | 2025-05-04 | 59645 | Update dependencies |
| 5.11.1 | 2025-04-27 | 58979 | Update dependencies |
| 5.11.0 | 2025-04-24 | 58637 | Promoting release candidate 5.11.0-rc.2 to a main version. |
| 5.11.0-rc.2 | 2025-04-18 | 58136 | Enable progressive rollout |
| 5.11.0-rc.1 | 2025-04-18 | 54162 | Migrate to low-code |
| 5.10.1 | 2025-04-17 | 58124 | Extend safe state to support nested states |
| 5.10.0 | 2025-04-17 | 58117 | Promoting release candidate 5.10.0-rc.1 to a main version. |
| 5.10.0-rc.1 | 2025-04-13 | 58060 | Migrate application_fees, authorizations, cardholders, cards, early_fraud_warnings, external_account_bank_accounts and external_account_cards to low-code |
| 5.9.2 | 2025-04-15 | 58072 | Add safe state data type handling |
| 5.9.1 | 2025-04-15 | 58068 | Add documentation url back in spec |
| 5.9.0 | 2025-04-14 | 58065 | Promoting release candidate 5.9.0-rc.1 to a main version. |
| 5.9.0-rc.1 | 2025-03-04 | 54162 | Migrate events, shipping_rates, balance_transactions, files and file_links to low-code |
| 5.8.14 | 2025-03-29 | 56871 | Update dependencies |
| 5.8.13 | 2025-03-22 | 56276 | Update dependencies |
| 5.8.12 | 2025-03-10 | 55682 | Promoting release candidate 5.8.10-rc.1 to a main version. |
| 5.8.11 | 2025-03-08 | 55598 | Update dependencies |
| 5.8.10-rc1 | 2025-02-22 | 53670 | Update pritbuffer logic |
| 5.8.9 | 2025-03-01 | 55117 | Update dependencies |
| 5.8.8 | 2025-02-28 | 54711 | Add retry error handler for `requests.exceptions.InvalidURL’ |
| 5.8.7 | 2025-02-22 | 54468 | Update dependencies |
| 5.8.6 | 2025-02-15 | 54067 | Update dependencies |
| 5.8.5 | 2025-02-08 | 52018 | Update dependencies |
| 5.8.4 | 2025-02-03 | 49940 | Update CDK version |
| 5.8.3 | 2025-01-11 | 46832 | Starting with this version, the Docker image is now rootless. Please note that this and future versions will not be compatible with Airbyte versions earlier than 0.64 |
| 5.8.2 | 2024-12-10 | 46499 | Source-Stripe: Refactor Customer Balance Transactions |
| 5.8.1 | 2024-12-08 | 46499 | Source-Stripe: Add new payout_balance_transactions incremental stream |
| 5.8.0 | 2024-10-12 | 46864 | Add incremental stream support to accounts stream |
| 5.7.0 | 2024-10-01 | 45860 | Add incremental stream support to invoice_line_items and subscription_items streams |
| 5.6.2 | 2024-10-05 | 43881 | Update dependencies |
| 5.6.1 | 2024-10-03 | 46327 | Bump the cdk to 5.10.2 to stop using PrintBuffer optimization due to record count mismatches |
| 5.6.0 | 2024-09-10 | 44891 | Update Payment Methods stream |
| 5.5.4 | 2024-09-09 | 45348 | Remove stripe python package |
| 5.5.3 | 2024-09-03 | 45101 | Fix regression following pagination issue fix |
| 5.5.2 | 2024-08-28 | 44862 | Fix RFR pagination issue |
| 5.5.1 | 2024-08-10 | 43105 | Update dependencies |
| 5.5.0 | 2024-08-08 | 43302 | Fix problem with state not updating and upgrade cdk 4 |
| 5.4.12 | 2024-07-31 | 41985 | Expand Invoice discounts and tax rates |
| 5.4.11 | 2024-07-27 | 42623 | Update dependencies |
| 5.4.10 | 2024-07-20 | 42305 | Update dependencies |
| 5.4.9 | 2024-07-13 | 41760 | Update dependencies |
| 5.4.8 | 2024-07-10 | 41477 | Update dependencies |
| 5.4.7 | 2024-07-09 | 40869 | Update dependencies |
| 5.4.6 | 2024-07-08 | 41044 | Use latest CDK version possible |
| 5.4.5 | 2024-06-25 | 40404 | Update dependencies |
| 5.4.4 | 2024-06-22 | 40040 | Update dependencies |
| 5.4.3 | 2024-06-06 | 39284 | [autopull] Upgrade base image to v1.2.2 |
| 5.4.2 | 2024-06-11 | 39412 | Removed invoice.upcomming event type from (incremental sync) for Invoices stream |
| 5.4.1 | 2024-06-11 | 39393 | Added missing event types (incremental sync) for Invoices stream |
| 5.4.0 | 2024-06-05 | 39138 | Fixed the Refunds stream missing data for the incremental sync |
| 5.3.9 | 2024-05-22 | 38550 | Update authenticator package |
| 5.3.8 | 2024-05-15 | 38248 | Replace AirbyteLogger with logging.Logger |
| 5.3.7 | 2024-04-24 | 36663 | Schema descriptions |
| 5.3.6 | 2024-04-18 | 37448 | Ensure AirbyteTracedException in concurrent CDK are emitted with the right type |
| 5.3.5 | 2024-04-18 | 37418 | Ensure python return code != 0 in case of error |
| 5.3.4 | 2024-04-11 | 37406 | Update CDK version to have partitioned state fix |
| 5.3.3 | 2024-04-11 | 37001 | Update airbyte-cdk to flush print buffer for every message |
| 5.3.2 | 2024-04-11 | 36964 | Update CDK version to fix breaking change before another devs work on it |
| 5.3.1 | 2024-04-10 | 36960 | Remove unused imports |
| 5.3.0 | 2024-03-12 | 35978 | Upgrade CDK to start emitting record counts with state and full refresh state |
| 5.2.4 | 2024-02-12 | 35137 | Fix license in pyproject.toml |
| 5.2.3 | 2024-02-09 | 35068 | Manage dependencies with Poetry. |
| 5.2.2 | 2024-01-31 | 34619 | Events stream concurrent on incremental syncs |
| 5.2.1 | 2024-01-18 | 34495 | Fix deadlock issue |
| 5.2.0 | 2024-01-18 | 34347 | Add new fields invoices and subscription streams. Upgrade the CDK for better memory usage. |
| 5.1.3 | 2023-12-18 | 33306 | Adding integration tests |
| 5.1.2 | 2024-01-04 | 33414 | Prepare for airbyte-lib |
| 5.1.1 | 2024-01-04 | 33926 | Update endpoint for bank_accounts stream |
| 5.1.0 | 2023-12-11 | 32908 | Read full refresh streams concurrently |
| 5.0.2 | 2023-12-01 | 33038 | Add stream slice logging for SubStream |
| 5.0.1 | 2023-11-17 | 32638 | Availability stretegy: check availability of both endpoints (if applicable) - common API + events API |
| 5.0.0 | 2023-11-16 | 32286 | Fix multiple issues regarding usage of the incremental sync mode for the Refunds, CheckoutSessions, CheckoutSessionsLineItems streams. Fix schemas for the streams: Invoices, Subscriptions, SubscriptionSchedule |
| 4.5.4 | 2023-11-16 | 32284 | Enable client-side rate limiting |
| 4.5.3 | 2023-11-14 | 32473 | Have all full_refresh stream syncs be concurrent |
| 4.5.2 | 2023-11-03 | 32146 | Fix multiple BankAccount issues |
| 4.5.1 | 2023-11-01 | 32056 | Use CDK version 0.52.8 |
| 4.5.0 | 2023-10-25 | 31327 | Use concurrent CDK when running in full-refresh |
| 4.4.2 | 2023-10-24 | 31764 | Base image migration: remove Dockerfile and use the python-connector-base image |
| 4.4.1 | 2023-10-18 | 31553 | Adjusted Setup Attempts and extended Checkout Sessions stream schemas |
| 4.4.0 | 2023-10-04 | 31046 | Added margins field to invoice_line_items stream. |
| 4.3.1 | 2023-09-27 | 30800 | Handle permission issues a non breaking |
| 4.3.0 | 2023-09-26 | 30752 | Do not sync upcoming invoices, extend stream schemas |
| 4.2.0 | 2023-09-21 | 30660 | Fix updated state for the incremental syncs |
| 4.1.1 | 2023-09-15 | 30494 | Fix datatype of invoices.lines property |
| 4.1.0 | 2023-08-29 | 29950 | Implement incremental deletes, add suggested streams |
| 4.0.1 | 2023-09-07 | 30254 | Fix cursorless incremental streams |
| 4.0.0 | 2023-08-15 | 29330 | Implement incremental syncs based on date of update |
| 3.17.4 | 2023-08-15 | 29425 | Revert 3.17.3 |
| 3.17.3 | 2023-08-01 | 28911 | Revert 3.17.2 and fix atm_fee property |
| 3.17.2 | 2023-08-01 | 28911 | Fix stream schemas, remove custom 403 error handling |
| 3.17.1 | 2023-08-01 | 28887 | Fix Invoices schema |
| 3.17.0 | 2023-07-28 | 26127 | Add Prices stream |
| 3.16.0 | 2023-07-27 | 28776 | Add new fields to stream schemas |
| 3.15.0 | 2023-07-09 | 28709 | Remove duplicate streams |
| 3.14.0 | 2023-07-09 | 27217 | Add ShippingRates stream |
| 3.13.0 | 2023-07-18 | 28466 | Pin source API version |
| 3.12.0 | 2023-05-20 | 26208 | Add new stream Persons |
| 3.11.0 | 2023-06-26 | 27734 | License Update: Elv2 stream |
| 3.10.0 | 2023-06-22 | 27132 | Add CreditNotes stream |
| 3.9.1 | 2023-06-20 | 27522 | Fix formatting |
| 3.9.0 | 2023-06-19 | 27362 | Add new Streams: Transfer Reversals, Setup Attempts, Usage Records, Transactions |
| 3.8.0 | 2023-06-12 | 27238 | Add Topups stream; Add Files stream; Add FileLinks stream |
| 3.7.0 | 2023-06-06 | 27083 | Add new Streams: Authorizations, Cardholders, Cards, Payment Methods, Reviews |
| 3.6.0 | 2023-05-24 | 25893 | Add ApplicationFeesRefunds stream with parent ApplicationFees |
| 3.5.0 | 2023-05-20 | 22859 | Add stream Early Fraud Warnings |
| 3.4.3 | 2023-05-10 | 25965 | Fix Airbyte date-time data-types |
| 3.4.2 | 2023-05-04 | 25795 | Added CDK TypeTransformer to guarantee declared JSON Schema data-types |
| 3.4.1 | 2023-04-24 | 23389 | Add customer_tax_ids to Invoices |
| 3.4.0 | 2023-03-20 | 23963 | Add SetupIntents stream |
| 3.3.0 | 2023-04-12 | 25136 | Add stream Accounts |
| 3.2.0 | 2023-04-10 | 23624 | Add new stream Subscription Schedule |
| 3.1.0 | 2023-03-10 | 19906 | Expand tiers when syncing Plans streams |
| 3.0.5 | 2023-03-25 | 22866 | Specified date formatting in specification |
| 3.0.4 | 2023-03-24 | 24471 | Fix stream slices for single sliced streams |
| 3.0.3 | 2023-03-17 | 24179 | Get customer’s attributes safely |
| 3.0.2 | 2023-03-13 | 24051 | Cache customers stream; Do not request transactions of customers with zero balance. |
| 3.0.1 | 2023-02-22 | 22898 | Add missing column to Subscriptions stream |
| 3.0.0 | 2023-02-21 | 23295 | Fix invoice schema |
| 2.0.0 | 2023-02-14 | 22312 | Another fix of Invoices stream schema + Remove http urls from openapi_spec.json |
| 1.0.2 | 2023-02-09 | 22659 | Set AvailabilityStrategy for all streams |
| 1.0.1 | 2023-01-27 | 22042 | Set AvailabilityStrategy for streams explicitly to None |
| 1.0.0 | 2023-01-25 | 21858 | Update the Subscriptions and Invoices stream schemas |
| 0.1.40 | 2022-10-20 | 18228 | Update the PaymentIntents stream schema |
| 0.1.39 | 2022-09-28 | 17304 | Migrate to per-stream states. |
| 0.1.38 | 2022-09-09 | 16537 | Fix redeem_by field type for customers stream |
| 0.1.37 | 2022-08-16 | 15686 | Fix the bug when the stream couldn’t be fetched due to limited permission set, if so - it should be skipped |
| 0.1.36 | 2022-08-04 | 15292 | Implement slicing |
| 0.1.35 | 2022-07-21 | 14924 | Remove additionalProperties field from spec and schema |
| 0.1.34 | 2022-07-01 | 14357 | Add external account streams - |
| 0.1.33 | 2022-06-06 | 13449 | Add semi-incremental support for CheckoutSessions and CheckoutSessionsLineItems streams, fixed big in StripeSubStream, added unittests, updated docs |
| 0.1.32 | 2022-04-30 | 12500 | Improve input configuration copy |
| 0.1.31 | 2022-04-20 | 12230 | Update connector to use a spec.yaml |
| 0.1.30 | 2022-03-21 | 11286 | Minor corrections to documentation and connector specification |
| 0.1.29 | 2022-03-08 | 10359 | Improved performance for streams with substreams: invoice_line_items, subscription_items, bank_accounts |
| 0.1.28 | 2022-02-08 | 10165 | Improve 404 handling for CheckoutSessionsLineItems stream |
| 0.1.27 | 2021-12-28 | 9148 | Fix date, arrival\_date fields |
| 0.1.26 | 2021-12-21 | 8992 | Fix type events.request in schema |
| 0.1.25 | 2021-11-25 | 8250 | Rearrange setup fields |
| 0.1.24 | 2021-11-08 | 7729 | Include tax data in checkout_sessions_line_items stream |
| 0.1.23 | 2021-11-08 | 7729 | Correct payment_intents schema |
| 0.1.22 | 2021-11-05 | 7345 | Add 3 new streams |
| 0.1.21 | 2021-10-07 | 6841 | Fix missing start_date argument + update json files for SAT |
| 0.1.20 | 2021-09-30 | 6017 | Add lookback_window_days parameter |
| 0.1.19 | 2021-09-27 | 6466 | Use start_date parameter in incremental streams |
| 0.1.18 | 2021-09-14 | 6004 | Fix coupons and subscriptions stream schemas by removing incorrect timestamp formatting |
| 0.1.17 | 2021-09-14 | 6004 | Add PaymentIntents stream |
| 0.1.16 | 2021-07-28 | 4980 | Remove Updated field from schemas |
| 0.1.15 | 2021-07-21 | 4878 | Fix incorrect percent_off and discounts data filed types |
| 0.1.14 | 2021-07-09 | 4669 | Subscriptions Stream now returns all kinds of subscriptions (including expired and canceled) |
| 0.1.13 | 2021-07-03 | 4528 | Remove regex for acc validation |
| 0.1.12 | 2021-06-08 | 3973 | Add AIRBYTE_ENTRYPOINT for Kubernetes support |
| 0.1.11 | 2021-05-30 | 3744 | Fix types in schema |
| 0.1.10 | 2021-05-28 | 3728 | Update data types to be number instead of int |
| 0.1.9 | 2021-05-13 | 3367 | Add acceptance tests for connected accounts |
| 0.1.8 | 2021-05-11 | 3368 | Bump CDK connectors |