Skip to main content

Overview

Integrate.io uses the API provided by Stripe to sync the data. Stripe API reference

Requirements

  • You need permissions to view the API access token.

Collections

Notes on specific collections:
  • refunds: incremental on created. Updates apply through refund.* events.
  • payment_methods: fetched per customer on initial sync. Updates apply through payment_method.* events.
  • dispute_balance_transactions: join table with id and dispute_id columns, sourced from the balance_transactions array on each dispute.
  • payment_intents: exposes latest_charge in place of the removed charges field.

Obtain access token

Follow these steps to create a private API key.
Stripe dashboard Developers tab navigation
  • Reveal the Secret key and copy and paste it into the input field below.
Stripe secret key revealed in the Developers section
  • Navigate to your Account page.
  • Copy and paste your account ID into the input field below.
Stripe Account settings page showing the account ID

Integrate.io dashboard fields for Stripe secret key and account ID

Restricted API keys

You can use a Stripe restricted key (a key that starts with rk_) instead of the full secret key. Restricted keys limit access to the Stripe resources you choose. Grant the key read permission for each resource you plan to sync. If the key is missing a permission, the connection test fails with the error message from Stripe. The message names the account, the permission to enable, and a link to edit the key in the Stripe dashboard:
Enable the named permission on the key in the Stripe dashboard, then test the connection again. Secret values, including the key itself, appear as [...] in error messages.
Last modified on October 27, 2026