Connect Recharge¶

Squoosh reads your Recharge order count. It does not yet change how your AI shoppers behave. This connection prepares successful subscription checkout orders and their country mix for inspection, without turning those counts into a conversion rate.

This connector has not been validated against a live account. It stays at the authentication stage. Connecting a token verifies Orders read access; it does not activate shopper calibration or automatic order refreshes.

What the connection does¶

The connector counts successful checkout orders created during the selected window. These are the first orders of subscriptions placed by shoppers. Recurring subscription renewals, unsuccessful orders and refunded orders are excluded. A healthy response containing no matching orders produces a real zero count.

Recharge does not provide site session counts through this API. Squoosh therefore reports an order count, never an orders-per-session conversion rate. Country totals describe orders, not your overall visitor audience. Neither the count nor this order-derived country mix currently changes shopper behavior.

Keep a supported traffic source connected for audience calibration. Squoosh does not currently divide Recharge orders by that source's sessions. Recharge orders can also appear in Shopify, so their counts must not be added together. The property pairing model permits only one conversion source; Recharge is not yet eligible to activate as that rate source.

Create a Recharge token¶

You need a Recharge Admin API token with Orders: Read access (read_orders). The token identifies the store, so there is no separate store ID or host to enter.

1. Open your Recharge merchant portal.
2. Go to Tools & apps → API tokens. Only the store owner can see this page by default.
3. Choose Create new under Admin tokens.
4. Enter a token name, such as Squoosh, and a contact email.
5. Set Orders to Read access. Squoosh does not need write access or the separate Store read permission.
6. Accept the API Terms of Service and choose Save.
7. Copy the token for the Squoosh connection.

See Recharge's API token instructions. Availability of the Admin API on every pricing tier has not been confirmed; ask Recharge Support if the token screen is unavailable.

Connect Recharge in Squoosh¶

1. Open Integrations in Squoosh.
2. Choose Recharge, then Connect.
3. Paste the token into Admin API token.
4. Choose Connect.

Squoosh verifies access with a single Orders request, including for a store with no orders. A successful check confirms authentication and the required scope. The beta connector remains awaiting live snapshot validation.

What Squoosh reads and never reads¶

The Orders endpoint returns whole order objects, which can include names, email addresses, full addresses, IP addresses, user agents, prices and line items. Squoosh discards those unused fields; it retains only the aggregate count, country buckets and quality metadata from this adapter. It never queries separate customer, payment, charge or subscription endpoints, and never writes to Recharge.

The token is kept in the connection's secret credentials and sent only through the X-Recharge-Access-Token header over HTTPS. It is never placed in a request URL, snapshot, warning or log. Requests pin API version 2021-11.

Limits and caveats¶

• Window: the last N full UTC days, excluding the current partial day. The standard calibration request is 30 days. Recharge's examples use calendar-date filters; boundary inclusivity is not documented, so a boundary discrepancy of up to one day remains possible until live validation.
• Read ceiling: up to 20 sequential pages of 250 orders, or 5,000 returned orders per snapshot. If the final allowed page still supplies a continuation cursor, Squoosh marks both the count and geo as truncated. A subset is not guaranteed to contain the most recent orders because list ordering is not established.
• Refresh budget: minimum refresh interval of 10 minutes. Recharge documents a standard per-token bucket of 40 calls replenished at 2 calls per second. On a rate-limit response, wait at least 2 seconds before retrying. Other applications sharing the token consume the same budget.
• Pagination: filters are repeated on cursor requests and checked again on returned rows. Unexpected rows are excluded with a warning. A full page without the documented next_cursor key is marked partial; Squoosh does not guess the alternative next key. Repeated order IDs are counted once and warned about; cursor cycles fail the read.
• Missing dimensions: no device mix, traffic channel mix or session denominator is available from this implementation. Countries come from orders, not visitor sessions.
• Shopify Checkout: whether all first checkout orders appear through this API is unverified. Before promotion, a known subscription checkout must be matched against its Recharge order. If that integration does not expose first orders, conversion data must be omitted with a warning rather than presented as zero.
• Retention: the documented 90-day charges limit is not an Orders retention guarantee. Windows beyond 90 days need live validation.
• Validation path: a Shopify development store with Recharge installed and Shopify's Bogus Gateway can supply test checkouts. There is no separate Recharge sandbox API host. See Creating a developer account.

Troubleshooting¶

Related¶

• Recharge Orders API
• Recharge cursor pagination
• Recharge API rate limits
• Connect Google Analytics
• Connect Shopify
• Connect a CSV / Excel import