Advanced Analytica Advanced Analytica: IBOM
← All connectors
Stripe logo

Source connector

Stripe

Set up Stripe as a source and move its data into your chosen destination.

Version 7.1.0 certified generally available

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

  1. Log in to your Stripe account.
  2. In the top navigation bar, click Developers.
  3. In the top-left corner, click API keys.
  4. Click + Create restricted key.
  5. Choose a Key name, then select Read for all available permissions.
  6. 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:

  1. Log into your Airbyte Cloud account.
  2. Click Sources, then click + New source.
  3. On the Set up the source page, select Stripe from the Source type dropdown.
  4. Enter a name for the Stripe connector.

Airbyte Open Source

  1. Go to the Airbyte Open Source dashboard.
  2. Click Sources, then click + New source.
  3. On the Set up the source page, select Stripe from the Source type dropdown.
  4. Enter a name for the Stripe connector.
  1. 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.

  2. For Secret Key, enter the restricted key you created for the connection.

  3. 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.

  4. (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.
  5. (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.

  6. (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.

  7. (Optional) For Accounts start date, enter when the Accounts stream should start reading connected accounts. Use a UTC date and time in the format YYYY-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. Persons reads its accounts from the Accounts stream. The persons belonging to excluded accounts are therefore also excluded.

  8. (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.

  9. (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.

  10. 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:

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 Fees
  • Application Fee Refunds
  • Authorizations
  • Bank Accounts
  • Cardholders
  • Charges
  • Checkout Sessions
  • Coupons
  • Credit Notes
  • Customers
  • Disputes
  • Early Fraud Warnings
  • External Account Bank Accounts
  • External Account Cards
  • Invoice Items
  • Invoice Line Items
  • Invoices
  • Payment Intents
  • Payment Methods
  • Payouts
  • Persons
  • Plans
  • Prices
  • Products
  • Promotion Codes
  • Refunds
  • Reviews
  • Setup Intents
  • Subscription Items
  • Subscription Schedule
  • Subscriptions
  • Top Ups
  • Transactions
  • Transfers

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 is updated, set from created)
  • Balance Transactions
  • Customer Balance Transactions
  • Events
  • File Links
  • Files
  • Setup Attempts
  • Shipping Rates
  • Transfer 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 Fees
  • Application Fee Refunds
  • Authorizations
  • Bank Accounts
  • Cardholders
  • Cards
  • Charges
  • Checkout Sessions
  • Checkout Session Line Items (cursor field is checkout_session_updated)
  • Coupons
  • Credit Notes
  • Customers
  • Disputes
  • Early Fraud Warnings
  • External Account Bank Accounts
  • External Account Cards
  • Invoice Items
  • Invoice Line Items (cursor field is invoice_updated)
  • Invoices
  • Payment Intents
  • Payment Methods
  • Payouts
  • Payout Balance Transactions
  • Promotion Codes
  • Persons
  • Plans
  • Prices
  • Products
  • Refunds
  • Reviews
  • Setup Intents
  • Subscription Schedule
  • Subscription Items (cursor field is subscription_updated)
  • Subscriptions
  • Top Ups
  • Transactions
  • Transfers

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/accounts in 30-day created windows. 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 Accounts has used since 7.0.3. Earlier connector versions read it without errors.
  • Stripe doesn’t return created for Standard connected accounts. Their updated value is the sync time, as in earlier versions.
  • The Persons stream 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 Accounts stream 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 Accounts
  • Coupons
  • Customers
  • External Account Bank Accounts
  • External Account Cards
  • Invoices
  • Invoice Items
  • Persons
  • Plans
  • Prices
  • Products
  • Subscriptions

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
VersionDatePull RequestSubject
7.1.02026-11-0390436Read accounts from /v1/accounts by created: incremental syncs pick up new connected accounts, full refreshes read parallel 30-day windows
7.0.72026-11-1091749Update dependencies
7.0.62026-11-0390261Make interrupted customer_balance_transactions backfills resumable; fail on 400/403 for that stream instead of silently skipping customers
7.0.52026-11-0190396Simplify HTTP error handling configuration with no change to which errors are skipped or fail the sync
7.0.42026-11-0390764Update dependencies
7.0.32026-10-2089581Read 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.22026-10-2089447Update dependencies
7.0.12026-10-1388397Opt in to TCP keepalive and request timeouts (30 s connect, 80 s read) so dropped connections fail and retry instead of hanging
7.0.02026-10-1387765Use Stripe’s current il_ line item IDs for invoice_line_items on incremental syncs. See the migration guide.
6.0.232026-10-1388809Update dependencies
6.0.222026-10-0688070Update dependencies
6.0.212026-09-2987375Update dependencies
6.0.202026-09-2286838Update dependencies
6.0.192026-09-2185087Fix 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.182026-09-1586254Update dependencies
6.0.172026-09-1185799Prevent the events-based invoice_line_items and subscription_items transformations from running when original_record is missing or empty.
6.0.162026-09-0885672Update dependencies
6.0.152026-08-1884768Update dependencies
6.0.142026-08-1784355Update events now win same-second cursor ties with creation events so the newer payload is kept at the destination.
6.0.132026-08-1184134Update dependencies
6.0.122026-08-0483634Update dependencies
6.0.112026-07-2883119Update dependencies
6.0.102026-07-2182611Update dependencies
6.0.92026-07-1482034Update dependencies
6.0.82026-06-3081285Update dependencies
6.0.72026-06-2380686Update dependencies
6.0.62026-06-1680070Update dependencies
6.0.52026-06-0979523Update dependencies
6.0.42026-06-0379042Update dependencies
6.0.32026-04-2877424Update dependencies
6.0.22026-04-2176777Update dependencies
6.0.12026-04-1376276Rename “concurrent workers” to “concurrent threads” in connector spec
6.0.02026-04-1376095Fix 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.232026-03-3175864Update dependencies
5.15.222026-03-1274770Upgrade CDK to 7.13.0
5.15.212026-03-0674342Promoting release candidate 5.15.21-rc.5 to a main version.
5.15.21-rc.52026-03-0674337Make 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.42026-03-0474290Lower 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.32026-03-0374259Fix cursor age validation to clear state before constructing full refresh stream, ensuring true full refresh from start_date
5.15.21-rc.22026-02-2574051Fix sync failure when unselected parent streams have stale cursor state during cursor age validation
5.15.21-rc.12026-02-2573646Add cursor age validation for StateDelegatingStream streams to prevent data loss when initial sync fails mid-way
5.15.202026-02-2473944Update dependencies
5.15.192026-02-1773466Update dependencies
5.15.182026-02-1273318Promoting release candidate 5.15.18-rc.1 to a main version.
5.15.18-rc.12026-02-0472432fix(source-stripe): Fix Missing ConcurrencyLevel & Reduce Default Step Size
5.15.172026-01-2772363fix(source-stripe): Add date filtering for checkout_sessions full refresh
5.15.162026-01-2072106Update dependencies
5.15.152026-01-1471614Update dependencies
5.15.142025-12-1870638Update dependencies
5.15.132025-11-2570048Update dependencies
5.15.122025-11-1869580Update dependencies
5.15.112025-10-2968994Update dependencies
5.15.102025-10-2168527Update dependencies
5.15.92025-10-1467472Update dependencies
5.15.82025-09-3066891Update dependencies
5.15.72025-09-2466367Update dependencies
5.15.62025-09-0966115Update dependencies
5.15.52025-08-2465489Update dependencies
5.15.42025-08-1064840Update dependencies
5.15.32025-08-0464484Fix memory issue by moving schema loaders out of $parameters
5.15.22025-08-0364439Update dependencies
5.15.12025-07-2660561Update dependencies
5.15.02025-07-2363743Promoting release candidate 5.15.0-rc.1 to a main version.
5.15.0-rc.12025-07-2163370Migrate to manifest-only format.
5.14.12025-07-1562893Increase the timeout for syncs that fail without any records to one day.
5.14.02025-07-1563303Promoting release candidate 5.14.0-rc.1 to a main version.
5.14.0-rc.12025-06-1260846Rollback Low Code per partition streams; update slicer for invoice_line_items and normalization for events based streams
5.13.02025-05-2260846Update subscription_items and usage_records stream to python implementation
5.12.02025-05-1259743Update invoice_line_items stream to python implementation
5.11.32025-05-1060053Update dependencies
5.11.22025-05-0459645Update dependencies
5.11.12025-04-2758979Update dependencies
5.11.02025-04-2458637Promoting release candidate 5.11.0-rc.2 to a main version.
5.11.0-rc.22025-04-1858136Enable progressive rollout
5.11.0-rc.12025-04-1854162Migrate to low-code
5.10.12025-04-1758124Extend safe state to support nested states
5.10.02025-04-1758117Promoting release candidate 5.10.0-rc.1 to a main version.
5.10.0-rc.12025-04-1358060Migrate application_fees, authorizations, cardholders, cards, early_fraud_warnings, external_account_bank_accounts and external_account_cards to low-code
5.9.22025-04-1558072Add safe state data type handling
5.9.12025-04-1558068Add documentation url back in spec
5.9.02025-04-1458065Promoting release candidate 5.9.0-rc.1 to a main version.
5.9.0-rc.12025-03-0454162Migrate events, shipping_rates, balance_transactions, files and file_links to low-code
5.8.142025-03-2956871Update dependencies
5.8.132025-03-2256276Update dependencies
5.8.122025-03-1055682Promoting release candidate 5.8.10-rc.1 to a main version.
5.8.112025-03-0855598Update dependencies
5.8.10-rc12025-02-2253670Update pritbuffer logic
5.8.92025-03-0155117Update dependencies
5.8.82025-02-2854711Add retry error handler for `requests.exceptions.InvalidURL’
5.8.72025-02-2254468Update dependencies
5.8.62025-02-1554067Update dependencies
5.8.52025-02-0852018Update dependencies
5.8.42025-02-0349940Update CDK version
5.8.32025-01-1146832Starting 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.22024-12-1046499Source-Stripe: Refactor Customer Balance Transactions
5.8.12024-12-0846499Source-Stripe: Add new payout_balance_transactions incremental stream
5.8.02024-10-1246864Add incremental stream support to accounts stream
5.7.02024-10-0145860Add incremental stream support to invoice_line_items and subscription_items streams
5.6.22024-10-0543881Update dependencies
5.6.12024-10-0346327Bump the cdk to 5.10.2 to stop using PrintBuffer optimization due to record count mismatches
5.6.02024-09-1044891Update Payment Methods stream
5.5.42024-09-0945348Remove stripe python package
5.5.32024-09-0345101Fix regression following pagination issue fix
5.5.22024-08-2844862Fix RFR pagination issue
5.5.12024-08-1043105Update dependencies
5.5.02024-08-0843302Fix problem with state not updating and upgrade cdk 4
5.4.122024-07-3141985Expand Invoice discounts and tax rates
5.4.112024-07-2742623Update dependencies
5.4.102024-07-2042305Update dependencies
5.4.92024-07-1341760Update dependencies
5.4.82024-07-1041477Update dependencies
5.4.72024-07-0940869Update dependencies
5.4.62024-07-0841044Use latest CDK version possible
5.4.52024-06-2540404Update dependencies
5.4.42024-06-2240040Update dependencies
5.4.32024-06-0639284[autopull] Upgrade base image to v1.2.2
5.4.22024-06-1139412Removed invoice.upcomming event type from (incremental sync) for Invoices stream
5.4.12024-06-1139393Added missing event types (incremental sync) for Invoices stream
5.4.02024-06-0539138Fixed the Refunds stream missing data for the incremental sync
5.3.92024-05-2238550Update authenticator package
5.3.82024-05-1538248Replace AirbyteLogger with logging.Logger
5.3.72024-04-2436663Schema descriptions
5.3.62024-04-1837448Ensure AirbyteTracedException in concurrent CDK are emitted with the right type
5.3.52024-04-1837418Ensure python return code != 0 in case of error
5.3.42024-04-1137406Update CDK version to have partitioned state fix
5.3.32024-04-1137001Update airbyte-cdk to flush print buffer for every message
5.3.22024-04-1136964Update CDK version to fix breaking change before another devs work on it
5.3.12024-04-1036960Remove unused imports
5.3.02024-03-1235978Upgrade CDK to start emitting record counts with state and full refresh state
5.2.42024-02-1235137Fix license in pyproject.toml
5.2.32024-02-0935068Manage dependencies with Poetry.
5.2.22024-01-3134619Events stream concurrent on incremental syncs
5.2.12024-01-1834495Fix deadlock issue
5.2.02024-01-1834347Add new fields invoices and subscription streams. Upgrade the CDK for better memory usage.
5.1.32023-12-1833306Adding integration tests
5.1.22024-01-0433414Prepare for airbyte-lib
5.1.12024-01-0433926Update endpoint for bank_accounts stream
5.1.02023-12-1132908Read full refresh streams concurrently
5.0.22023-12-0133038Add stream slice logging for SubStream
5.0.12023-11-1732638Availability stretegy: check availability of both endpoints (if applicable) - common API + events API
5.0.02023-11-1632286Fix 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.42023-11-1632284Enable client-side rate limiting
4.5.32023-11-1432473Have all full_refresh stream syncs be concurrent
4.5.22023-11-0332146Fix multiple BankAccount issues
4.5.12023-11-0132056Use CDK version 0.52.8
4.5.02023-10-2531327Use concurrent CDK when running in full-refresh
4.4.22023-10-2431764Base image migration: remove Dockerfile and use the python-connector-base image
4.4.12023-10-1831553Adjusted Setup Attempts and extended Checkout Sessions stream schemas
4.4.02023-10-0431046Added margins field to invoice_line_items stream.
4.3.12023-09-2730800Handle permission issues a non breaking
4.3.02023-09-2630752Do not sync upcoming invoices, extend stream schemas
4.2.02023-09-2130660Fix updated state for the incremental syncs
4.1.12023-09-1530494Fix datatype of invoices.lines property
4.1.02023-08-2929950Implement incremental deletes, add suggested streams
4.0.12023-09-0730254Fix cursorless incremental streams
4.0.02023-08-1529330Implement incremental syncs based on date of update
3.17.42023-08-1529425Revert 3.17.3
3.17.32023-08-0128911Revert 3.17.2 and fix atm_fee property
3.17.22023-08-0128911Fix stream schemas, remove custom 403 error handling
3.17.12023-08-0128887Fix Invoices schema
3.17.02023-07-2826127Add Prices stream
3.16.02023-07-2728776Add new fields to stream schemas
3.15.02023-07-0928709Remove duplicate streams
3.14.02023-07-0927217Add ShippingRates stream
3.13.02023-07-1828466Pin source API version
3.12.02023-05-2026208Add new stream Persons
3.11.02023-06-2627734License Update: Elv2 stream
3.10.02023-06-2227132Add CreditNotes stream
3.9.12023-06-2027522Fix formatting
3.9.02023-06-1927362Add new Streams: Transfer Reversals, Setup Attempts, Usage Records, Transactions
3.8.02023-06-1227238Add Topups stream; Add Files stream; Add FileLinks stream
3.7.02023-06-0627083Add new Streams: Authorizations, Cardholders, Cards, Payment Methods, Reviews
3.6.02023-05-2425893Add ApplicationFeesRefunds stream with parent ApplicationFees
3.5.02023-05-2022859Add stream Early Fraud Warnings
3.4.32023-05-1025965Fix Airbyte date-time data-types
3.4.22023-05-0425795Added CDK TypeTransformer to guarantee declared JSON Schema data-types
3.4.12023-04-2423389Add customer_tax_ids to Invoices
3.4.02023-03-2023963Add SetupIntents stream
3.3.02023-04-1225136Add stream Accounts
3.2.02023-04-1023624Add new stream Subscription Schedule
3.1.02023-03-1019906Expand tiers when syncing Plans streams
3.0.52023-03-2522866Specified date formatting in specification
3.0.42023-03-2424471Fix stream slices for single sliced streams
3.0.32023-03-1724179Get customer’s attributes safely
3.0.22023-03-1324051Cache customers stream; Do not request transactions of customers with zero balance.
3.0.12023-02-2222898Add missing column to Subscriptions stream
3.0.02023-02-2123295Fix invoice schema
2.0.02023-02-1422312Another fix of Invoices stream schema + Remove http urls from openapi_spec.json
1.0.22023-02-0922659Set AvailabilityStrategy for all streams
1.0.12023-01-2722042Set AvailabilityStrategy for streams explicitly to None
1.0.02023-01-2521858Update the Subscriptions and Invoices stream schemas
0.1.402022-10-2018228Update the PaymentIntents stream schema
0.1.392022-09-2817304Migrate to per-stream states.
0.1.382022-09-0916537Fix redeem_by field type for customers stream
0.1.372022-08-1615686Fix the bug when the stream couldn’t be fetched due to limited permission set, if so - it should be skipped
0.1.362022-08-0415292Implement slicing
0.1.352022-07-2114924Remove additionalProperties field from spec and schema
0.1.342022-07-0114357Add external account streams -
0.1.332022-06-0613449Add semi-incremental support for CheckoutSessions and CheckoutSessionsLineItems streams, fixed big in StripeSubStream, added unittests, updated docs
0.1.322022-04-3012500Improve input configuration copy
0.1.312022-04-2012230Update connector to use a spec.yaml
0.1.302022-03-2111286Minor corrections to documentation and connector specification
0.1.292022-03-0810359Improved performance for streams with substreams: invoice_line_items, subscription_items, bank_accounts
0.1.282022-02-0810165Improve 404 handling for CheckoutSessionsLineItems stream
0.1.272021-12-289148Fix date, arrival\_date fields
0.1.262021-12-218992Fix type events.request in schema
0.1.252021-11-258250Rearrange setup fields
0.1.242021-11-087729Include tax data in checkout_sessions_line_items stream
0.1.232021-11-087729Correct payment_intents schema
0.1.222021-11-057345Add 3 new streams
0.1.212021-10-076841Fix missing start_date argument + update json files for SAT
0.1.202021-09-306017Add lookback_window_days parameter
0.1.192021-09-276466Use start_date parameter in incremental streams
0.1.182021-09-146004Fix coupons and subscriptions stream schemas by removing incorrect timestamp formatting
0.1.172021-09-146004Add PaymentIntents stream
0.1.162021-07-284980Remove Updated field from schemas
0.1.152021-07-214878Fix incorrect percent_off and discounts data filed types
0.1.142021-07-094669Subscriptions Stream now returns all kinds of subscriptions (including expired and canceled)
0.1.132021-07-034528Remove regex for acc validation
0.1.122021-06-083973Add AIRBYTE_ENTRYPOINT for Kubernetes support
0.1.112021-05-303744Fix types in schema
0.1.102021-05-283728Update data types to be number instead of int
0.1.92021-05-133367Add acceptance tests for connected accounts
0.1.82021-05-113368Bump CDK connectors
Advanced Analytica

Most businesses are sitting on information they can’t use at speed. The people who hold it are busy, and when they leave, the knowledge goes with them. The documents are static, and the processes around them weren’t designed for AI.

Advanced Analytica works with these businesses to turn that information into structured data assets. Once they're integrated, AI systems can govern it, and the business can use it. We bring in the strategy, the specification and the AI skills to rework how the business operates.

MOVE FAST. STAY SAFE.