CONNECT APP
Build with Recharge
Commerce
- API key
MCP
Give your agent Recharge tools
Every Recharge action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Recharge account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "recharge",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Cancel Subscription:
const result = await mcp.callTool({
name: "recharge-cancel-subscription",
arguments: {
subscriptionId: "Subscription ID",
cancellationReason: "Cancellation Reason",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "recharge",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Cancel Subscription:
result = await session.call_tool("recharge-cancel-subscription", {
"subscriptionId": "Subscription ID",
"cancellationReason": "Cancellation Reason",
})API PROXY
Call the Recharge API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Recharge API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.rechargeapps.com/customers",
})
// Any allowed Recharge endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.rechargeapps.com/customers
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkucmVjaGFyZ2VhcHBzLmNvbS9jdXN0b21lcnM?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Recharge actions from your backend
Connect a user's Recharge account once, then run Cancel Subscription on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "recharge-cancel-subscription",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
recharge: { authProvisionId: "apn_xxxxxxx" },
subscriptionId: "Subscription ID",
cancellationReason: "Cancellation Reason",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="recharge-cancel-subscription",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"recharge": {"authProvisionId": "apn_xxxxxxx"},
"subscriptionId": "Subscription ID",
"cancellationReason": "Cancellation Reason",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "recharge-cancel-subscription",
"configured_props": {
"recharge": { "authProvisionId": "apn_xxxxxxx" },
"subscriptionId": "Subscription ID",
"cancellationReason": "Cancellation Reason"
}
}'TOOLS
Recharge actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Cancel Subscription
actionCancels an existing subscription. See the documentationWritev0.0.2 -
Create Customer
actionCreates a customer. See the documentationWritev0.0.2 -
Create Subscription
actionCreates a new subscription allowing a customer to subscribe to a product. See the documentationWritev0.0.2 -
List Address ID Options
actionRetrieves available options for the Address ID field.Read-onlyv0.0.1 -
List Customer ID Options
actionRetrieves available options for the Customer ID field.Read-onlyv0.0.1 -
List External Variant ID Options
actionRetrieves available options for the External Variant ID field.Read-onlyv0.0.1 -
List Subscription ID Options
actionRetrieves available options for the Subscription ID field.Read-onlyv0.0.1 -
Update Customer
actionUpdates an existing customer's details. See the documentationWritev0.0.2
EVENTS
Recharge triggers
Event sources your backend can deploy for users and receive through a webhook.
-
New Customer Created (Instant)
triggerEmit new event when a new customer is created.Instantv0.0.1 -
New Order Created (Instant)
triggerEmit new event when a new order is created.Instantv0.0.1 -
New Subscription Created (Instant)
triggerEmit new event when a new subscription is created.Instantv0.0.1
MULTI-APP
Use Recharge with other popular apps
Most products don't stop at one integration. Pair Recharge with the other apps your users rely on, and ship use cases that span both.
- App slug
- recharge
- Authentication
- API key
- Categories
- Commerce
- Actions
- 8
- Triggers
- 3
- API proxy
- Available