Support for Stripe Organization API keys in the Stripe connector
AnsweredWhich connector?:
Stripe
Additional details:
Stripe Organizations allow grouping multiple Stripe accounts and using a single Organization API key (sk_org_...) to access all of them. Currently, the Fivetran Stripe connector does not support these keys: the setup test fails because Stripe requires the Stripe-Context header to identify the target account.
Use case: Our Stripe organization per country contains two accounts (collections and deposits). We would like a single Fivetran connection per organization that syncs all its accounts into one destination schema, sending the appropriate Stripe-Context header for each account and adding an account identifier column to each table.
Today we need one connection and one account-level API key per Stripe account, and we consolidate the data downstream, which adds maintenance and deduplication work.
Related support ticket: 418309
-
Official comment
Hi Patricia,
Thanks for the suggestion! I'd love to understand this request in more detail before we evaluate it.
Could you elaborate on your current workflow? What kind of deduplication across the two accounts needs to occur in your downstream pipelines? Do you plan on adding connections for more organizations in the future? If not, is your downstream pipeline a manageable workaround for the time being? What would make you want to change from what you have to one connection?
Thanks,
Sadie
Please sign in to leave a comment.
Comments
1 comment