> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/connect-sources/data-sources/connect-data-sources/recharge.md). # Recharge ## 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 with the exact error message. We'll trace the request and tell you which scope is missing. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.chord.co/connect-sources/data-sources/connect-data-sources/recharge.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.