Create a Recharge subscription for a Shopify customer and manage its lifecycle via the Recharge API
domain: developer.rechargepayments.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate requests by passing your Recharge API key in the X-Recharge-Access-Token header on every request to https://api.rechargeapps.com
Create a subscription with POST /subscriptions, supplying customer_id, address_id, next_charge_scheduled_at, order_interval_unit (day/week/month), order_interval_frequency, and charge_interval_frequency
Retrieve a customer's active subscriptions with GET /subscriptions?customer_id=CUSTOMER_ID&status=active using cursor-based pagination (next_cursor param) rather than the deprecated page-based pagination
Update shipping interval with PATCH /subscriptions/SUBSCRIPTION_ID, setting order_interval_frequency and charge_interval_frequency fields
Cancel a subscription with POST /subscriptions/SUBSCRIPTION_ID/cancel with a required cancellation_reason string in the body
Monitor lifecycle events by registering webhooks for subscription/created, subscription/updated, and subscription/cancelled via POST /webhooks
Known gotchas
The 2021-11 API version uses cursor pagination; page-based pagination is limited to 100 results and is deprecated — always use cursor for production data exports
Cancellation requires a non-empty cancellation_reason field; omitting it returns a 422 validation error
Recharge operates its own charge schedule separate from Shopify orders — changes to next_charge_scheduled_at do not propagate back to Shopify draft orders automatically
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?