Release all connectors affected by namespace change. Includes all JDBC sources and destinations. Also add documentation for normalisation. Prerequisite to actually releasing 0.21.0-alpha.
2.1 KiB
Stripe
Overview
The Stripe source supports both Full Refresh and Incremental syncs. You can choose if this connector will copy only the new or updated data, or all rows in the tables and columns you set up for replication, every time a sync is run.
This Stripe source is based on the Singer Stripe Tap.
Output schema
Several output streams are available from this source (customers, charges, invoices, subscriptions, etc.) For a comprehensive output schema look at the Singer tap schema files.
Data type mapping
The Stripe API uses the same JSONSchema types that Airbyte uses internally (string, date-time, object, array, boolean, integer, and number), so no type conversions happen as part of this source.
Features
| Feature | Supported? |
|---|---|
| Full Refresh Sync | Yes |
| Incremental - Append Sync | Yes |
| Replicate Incremental Deletes | Coming soon |
| SSL connection | Yes |
| Namespaces | No |
Performance considerations
The Stripe connector should not run into Stripe API limitations under normal usage. Please create an issue if you see any rate limit issues that are not automatically retried successfully.
Getting started
Requirements
- Stripe Account
- Stripe API Secret Key
Setup guide
Visit the Stripe API Keys page in the Stripe dashboard to access the secret key for your account. Secret keys for the live Stripe environment will be prefixed with sk_live_or rk_live.
We recommend creating a restricted key specifically for Airbyte access. This will allow you to control which resources Airbyte should be able to access. For ease of use, we recommend using read permissions for all resources and configuring which resource to replicate in the Airbyte UI.
If you would like to test Airbyte using test data on Stripe, sk_test_ and rk_test_ API keys are also supported.