> For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandium.com/connectors/connectors-101/recharge.md).
# ReCharge
Set up the ReCharge connector in Pandium using an API key so tenants can authenticate securely and sync subscription billing, customer retention data, and recurring payment information.
## **Connector Overview**
ReCharge is a platform that automates billing and enhances customer retention. It offers flexible tools for integrations, efficient workflows, and tailored experiences, all designed to drive growth and increase revenue for subscription-based businesses
## **Authentication Type**
Basic
## **Webhook Supported**
No
## **Secrets**
* PAN\_SEC\_RECHARGE\_API\_KEY
## **API Client Supported**
No
## **Requirements for Provisioning**
In order to provision your connector, the following ReCharge information must be gathered:
* API Key
To obtain the information required for setting up, perform the following steps:
1. Login to the [Recharge merchant Portal](https://admin.rechargeapps.com/admin/login).
2. Navigate to Tools & apps and click API tokens.
3. On the following page, click Create an API Token to generate a new token for your store.
4. Use the Details fields to set a name and contact email for the token.
5. Select No access, Read access, or Read and Write access to set the scope permissions you'd like to grant the token.
6. Click Save to create your token
## **API Resources**
For more information on how to utilize the Recharge API, feel free to reference the following [documentation](https://docs.getrecharge.com/docs/api-getting-started).
---
# 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.pandium.com/connectors/connectors-101/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.
