Common Issues

Connection issues

Authentication failed — invalid API key

Double-check that you've copied the full API key from Chargify without any leading or trailing spaces. In Chargify, go to Settings → API Keys to verify the key is active. Note that API keys are site-specific — make sure you're using the key from the correct Chargify site.

Subdomain not recognized

The subdomain field should contain only the prefix of your Chargify URL — not the full URL. For example, if your Chargify portal is at acme.chargify.com, enter acme, not https://acme.chargify.com.

Missing data

Some subscriptions or customers are missing from the export

Chargify's API may exclude soft-deleted or archived records by default. If you're missing canceled subscriptions or inactive customers, check whether those records still exist in your Chargify account. Records that have been fully purged from Chargify will not appear in the export.

Coupons entity returns an empty result

If you haven't created any coupons in Chargify, the entity will return an empty dataset — this is expected behavior. Also confirm that coupons are scoped to the correct product family in Chargify.

Permission errors

API key returns a 403 Forbidden error

The API key you're using may have restricted permissions. Chargify supports read-only API keys — make sure the key has at least read access to the entities you're trying to export. If you're unsure, generate a new key in Settings → API Keys with full read permissions.

Data discrepancies

Revenue totals don't match what I see in Chargify's dashboard

Chargify stores all monetary values in cents. If your destination tool is displaying raw values without dividing by 100, the numbers will appear 100x too large. Add a calculated column or formula in your destination to convert cents to dollars.

Also note that Chargify dashboards may apply their own filters (e.g., excluding refunds or credits) that differ from what Coupler.io exports.

Transaction counts differ from the Chargify UI

The Transactions entity includes all transaction types — payments, refunds, credits, and adjustments. Chargify's UI may filter these differently depending on which report you're viewing. Filter by transaction_type in your destination to isolate the specific transaction type you want to reconcile.

Rate limits

Data flow fails with a rate limit or 429 error

Chargify enforces API rate limits per site. If you're syncing multiple entities in quick succession or have very large data volumes, you may hit these limits. Try running each entity as a separate data flow and space out your scheduled refreshes. If the problem persists, contact Chargify support to check your site's rate limit tier.