Skip to main content Skip to complementary content
Already have an account? Sign in

Chargify (v1)

Last updated: 9/15/2026

Chargify integration summary

Stitch’s Chargify integration replicates data using the Chargify API. Refer to the Schema section for a list of objects available for replication.

Chargify feature snapshot

A high-level look at Stitch's Chargify (v1) integration, including release status, useful links, and the features supported in Stitch.

STITCH
Release status

Beta

Supported by

Singer Community

Stitch plan

Standard

API availability

Available

Singer GitHub repository

singer-io/tap-chargify

REPLICATION SETTINGS
Anchor Scheduling

Supported

Advanced Scheduling

Supported

Table-level reset

Unsupported

Configurable Replication Methods

Unsupported

DATA SELECTION
Table selection

Supported

Column selection

Supported

Select all

Supported

TRANSPARENCY
Extraction Logs

Supported

Loading Reports

Supported

Connecting Chargify

Chargify setup requirements

To set up Chargify in Stitch, you need:

  • Owner or Admin access in Chargify. A user with either level of access is required to create an API key for Stitch.

Step 1: Create a Chargify API key

  1. Sign into your Chargify account as a user with either Owner or Admin access.
  2. Navigate to Config > Integrations.
  3. Click New API Key.
  4. Copy your API key somewhere secure.

Step 2: Add Chargify as a Stitch data source

  1. Sign into your Stitch account.
  2. On the Stitch Dashboard page, click the Add Integration button.

  3. Click the Chargify icon.

  4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

    For example, the name “Stitch Chargify” would create a schema called stitch_chargify in the destination. Note: Schema names cannot be changed after you save the integration.

  5. In the API Key field, paste the API key you created in Step 1.
  6. In the Subdomain field, enter your Chargify subdomain. For example: If the full URL of your Chargify site were https://stitch.my-chargify-site.com, this value would be stitch.

Step 3: Define the historical replication start date

The Sync Historical Data setting defines the starting date for your Chargify integration. This means that data equal to or newer than this date will be replicated to your data warehouse.

Change this setting if you want to replicate data beyond Chargify’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.

Step 4: Create a replication schedule

In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Chargify integrations support the following replication scheduling methods:

To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.

Step 5: Set objects to replicate

The last step is to select the tables and columns you want to replicate. Learn about the available tables for this integration.

Note: If a replication job is currently in progress, new selections won’t be used until the next job starts.

For Chargify integrations, you can select:

  1. Individual tables and columns

  2. All tables and columns

Click the tabs to view instructions for each selection method.

  1. In the integration’s Tables to Replicate tab, locate a table you want to replicate.
  2. To track a table, click the checkbox next to the table’s name. A blue checkmark means the table is set to replicate.

  3. To track a column, click the checkbox next to the column’s name. A blue checkmark means the column is set to replicate.

  4. Repeat this process for all the tables and columns you want to replicate.
  5. When finished, click the Finalize Your Selections button at the bottom of the screen to save your selections.
  1. Click into the integration from the Stitch Dashboard page.
  2. Click the Tables to Replicate tab.

  3. In the list of tables, click the box next to the Table Names column.
  4. In the menu that displays, click Track all Tables and Fields:

    The Track all Tables and Fields menu in the Tables to Replicate tab
    The Track all Tables and Fields menu in the Tables to Replicate tab

  5. Click the Finalize Your Selections button at the bottom of the page to save your data selections.

Initial and historical replication jobs

After you finish setting up Chargify, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.

Chargify table reference

components

The components table contains info about components associated with a product family in Chargify.

Replication Method

Full Table

Primary Key

id

Useful links

components schema on GitHub

Chargify API method

coupons

The coupons table contains info about coupons associated with a product family in Chargify.

Replication Method

Full Table

Primary Key

id

Useful links

coupons schema on GitHub

Chargify API method

customers

The customers table contains info about customers associated with your Chargify site.

Replication Method

Full Table

Primary Key

id

Useful links

customers schema on GitHub

Chargify API method

events

The events table contains info about activity on your Chargify site.

Replication Method

Full Table

Primary Key

id

Useful links

events schema on GitHub

Chargify API method

invoices

The invoices table contains info about invoices in your Chargify instance.

Replication Method

Key-based Incremental

Primary Key

id

Useful links

invoices schema on GitHub

Chargify API method

price_points

The price_points table contains info about product price points in your Chargify instance.

Replication Method

Full Table

Primary Key

id

Useful links

price_points schema on GitHub

Chargify API method

product_families

The product_families table contains info about product families in your Chargify instance. Product families house your products, components, and coupons and are used to categorize products, product levels, or service offerings to your subscribers.

Replication Method

Full Table

Primary Key

id

Useful links

product_families schema on GitHub

Chargify API method

products

The products table contains info about the prodcts in your Chargify instance.

Replication Method

Full Table

Primary Key

id

Useful links

products schema on GitHub

Chargify API method

statements

The statements table contains info about the statements in your Chargify instance. Statements show all account activity for a specific usage period and are similar to invoices, as they can be marked as currently paid or unpaid.

Replication Method

Full Table

Primary Key

id

Useful links

statements schema on GitHub

Chargify API method

subscriptions

The subscriptions table contains info about the subscriptions in your Chargify instance.

Replication Method

Full Table

Primary Key

id

Useful links

subscriptions schema on GitHub

Chargify API method

transactions

The transactions table contains info about the transactions for your Chargify site.

Replication Method

Key-based Incremental

Loading Behavior

Append-Only

Primary Key

id

Replication Key

created_at

Useful links

transactions schema on GitHub

Chargify API method

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!