# Recharge integrations: subscriptions and customers

> Create a subscription, create a customer and update an order in Recharge, and start a workflow when Recharge sends “Subscription created”.

**Canonical page:** https://tray.ai/connectors/recharge-integrations/
**Categories:** Finance
**Connects through:** HTTP Connector

## Overview

Recharge is a subscription billing platform for ecommerce stores, managing recurring orders, customer subscriptions, charges, discounts and checkout for brands selling on Shopify and other storefronts. Tray.ai connects to Recharge through the HTTP Connector, so your workflows can call the Recharge API alongside the rest of your stack.

## Use cases

### Subscriptions

Read, create, update, and delete subscriptions in Recharge from any Tray.ai workflow. The Recharge API covers calls such as list subscriptions and create a subscription.

- List subscriptions
- Create a subscription
- Update a subscription

### Customers

Read, create, update, and delete customers in Recharge from any Tray.ai workflow. The Recharge API covers calls such as list customers and create a customer.

- List customers
- Create a customer
- Update a customer

### Charges

Read charges in Recharge from any Tray.ai workflow. The Recharge API covers calls such as list charges and skip a charge.

- List charges
- Skip a charge
- Refund a charge

### Orders

Read, update, and delete orders in Recharge from any Tray.ai workflow. The Recharge API covers calls such as list orders and update an order.

- List orders
- Update an order
- Clone an order

### Addresses

Read, create, update, and delete addresses in Recharge from any Tray.ai workflow. The Recharge API covers calls such as list addresses and create an address.

- List addresses
- Create an address
- Update an address

### Discounts

Read, create, update, and delete discounts in Recharge from any Tray.ai workflow. The Recharge API covers calls such as list discounts and create a discount.

- List discounts
- Create a discount
- Update a discount

## Challenges Tray.ai solves

### Keeping Recharge credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Recharge credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Recharge API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Recharge API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Recharge?

Yes. Tray.ai connects to Recharge through the HTTP Connector, which calls the Recharge API directly. Any call the Recharge API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Recharge?

The Recharge API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Recharge connector?

Recharge runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Recharge connector from the Recharge API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/