Recharge

connect your recharge subscription data to chord recharge is the subscription management platform that powers recurring billing, customer portals, and lifecycle events for many subscription brands on shopify chord ingests subscription, order, charge, customer, and product data from recharge so you can model retention, churn, and lifetime value alongside the rest of your stack what chord ingests from recharge chord pulls 12 datasets from your recharge account each dataset becomes its own table in your chord snowflake schema subscriptions active and historical subscription records frequency, status, line items, next billing date orders subscription driven orders, including cart and shipping details charges \ individual charge attempts and outcomes successes, failures, retries customers customer profiles linked to subscriptions addresses shipping and billing addresses on customer accounts discounts discount codes and their usage on subscriptions events subscription lifecycle events cancellations, pauses, reactivations, swaps, skipped charges collections product collections and their merchandising structure plans selling plans (frequency × price tiers) attached to products one time products one time products purchased alongside subscriptions bundle selections choices made within bundle subscriptions generate a recharge api token you'll need a recharge api token with the seven read scopes listed below the token is created in the recharge merchant admin and pasted into chord hub heads up only store owners can access the api tokens page by default if you're a staff user, ask your store owner to either generate the token for you or grant your account api token permissions first 1 log in to the recharge merchant portal 2 in the left sidebar, click tools & apps , then click api tokens 3 click create an api token , then choose admin api token 4 fill in the details section token name — something recognizable, e g chord data sync contact email — an inbox at your company that recharge can reach about this token 5 under permissions , set the following required scopes below as read access (leave everything else as no access ) required scopes chord needs all seven of these read scopes for the connector to pull every dataset cleanly make sure each one is enabled before saving the token read subscriptions subscriptions, one time products, bundle selections read orders orders, charges read customers customers, addresses read discounts discounts read events events read plans plans read products products connect the token in chord 1 open chord hub and go to data sources → add source 2 pick recharge from the data source list 3 paste the token you just copied into the api token field 4 click save — chord makes a test call against your recharge account to confirm the token works and has all seven read scopes 5 the first sync kicks off automatically; subsequent syncs run on your tenant's standard ingestion schedule troubleshooting what does the validate step actually check? chord makes a small read against scoped endpoints and confirms the token returns data without a permission error it does not pull or store any records, that happens on the first scheduled sync after you save the credential the validate step failed with a scope error what now? recharge tokens are editable after created, you can add scopes to an existing token go back to tools & apps → api tokens in recharge, edit the existing token with all seven read scopes enabled, and then, go back to chord and test the connection once again do recharge api tokens expire? no tokens stay valid until a store owner manually revokes them in tools & apps → api tokens if a previously working token suddenly fails, check that page first to confirm it's still listed and active how do i rotate the token? generate a new token in recharge with the same seven read scopes, paste it into the same chord credential entry, and save chord uses the new token on the next scheduled sync once you've confirmed the new token validates and the next sync runs cleanly, delete the old token from recharge who can see the token after it's saved in chord? the token value is encrypted at rest in chord hub and is never displayed back in the ui you can rotate or delete it any time, but you can't view the original value once it's saved need help? if you hit a scope or permission issue you can't resolve, reach out to help\@chord co mailto\ help\@chord co with the exact error message we'll trace the request and tell you which scope is missing