Major

Recharge AI: API Guide, Agents and Workflow Automations

Understand Recharge's native AI, eight useful API operations, and how to build governed subscriber operations with Major apps, judgment agents, and approval workflows.

Ritvij GautamUpdated
packing ecommerce orders warehouse (Recharge AI agents and automations)

Recharge manages recurring products, billing, and subscriber experiences. Recharge AI includes native assistance and conversational subscription management. This guide covers those features, the Recharge API, and how Major adds governed cross-system automation.

On Major, agents build deterministic apps that hold subscriber state and review queues. Agents make judgment calls, while workflows coordinate retrieval, approvals, and authorized actions.

What Recharge is and who relies on it

Recharge is subscription commerce software for merchants that sell recurring products. Its getting-started guide describes product management, storefront subscription options, checkout, backend processing, and merchant and customer portals.

Subscription operations teams use the merchant portal to maintain subscriber records and subscription products. Customers use their portal to change delivery frequency, review purchases, and update billing information. Developers use the API when a merchant needs a custom storefront, customer portal, or backend integration.

Retention managers care about a different slice of the same records: why someone canceled, what they purchased, and whether outreach would actually help. Support teams need to distinguish an intentional cancellation from a billing problem before offering a remedy.

Major fits where these jobs cross systems. An operations app can retain Recharge identity mappings, review ownership, and action history. An agent can interpret a subscriber's explanation alongside support context. The workflow can then route the proposed response without turning every predictable lookup into another reasoning task.

Recharge AI and its built-in features

Recharge already offers AI inside its own product. Remi is a dashboard assistant that answers questions using store data, including churn, retention, subscription revenue, failed charges, and configuration. It can explain charge failures and provide next steps informed by the merchant's setup.

Concierge SMS supports conversational subscriber interactions over text. Recharge describes interpreting requests, helping subscribers adjust or skip orders, and escalating situations to the team with context. These capabilities are useful when the work belongs within Recharge's subscriber experience.

Major adds a durable operating layer around that experience. A cancellation might need comparison with an unresolved support case, a marketing suppression record, and a previously approved concession. An agent on Major can weigh that context and recommend the next action.

The app stores evidence, proposed actions, and outcomes. The workflow enforces approvals and delivery rules. Native Recharge features remain useful; the choice is which system should own each part of the process, not whether every interaction needs another agent.

How Recharge connects to Major

Recharge has no native or Pipedream connector in the catalog: it connects as a custom API connector, with base URL and authentication configured once by IT. Do not confuse Recharge's public API availability with a prebuilt Major connector.

The documented API base URL and authentication header are https://api.rechargeapps.com and X-Recharge-Access-Token. IT configures these centrally, chooses the supported API version, and assigns the smallest useful permissions. The current reference shows X-Recharge-Version: v2; pin and test the version rather than relying on a store default.

Credentials remain in Major's connector vault, never in code or prompts. SSO, RBAC, and audit logs cover the apps, agents, and workflows that use the connection. Give a read-only retention process different authority from an approved subscription-change process.

Major orchestrates Recharge; it never replaces it. Recharge remains the subscription system of record. Major holds operational state such as evidence snapshots, approval records, and cross-system delivery status, rather than pretending its cached copy is authoritative for billing.

Recharge API guide for useful operations

Authentication and operating constraints

Recharge supports merchant API tokens and encourages OAuth for partner apps, according to its security guide. The authentication reference names read_subscriptions, read_customers, and read_orders. Start there; add write_subscriptions only when approved mutations are necessary. Charges use the order read permission, not an invented charge scope.

Cursor pagination returns next_cursor and a previous cursor. Send the returned value as cursor, with limit. The pagination guide documents 50 records by default and 250 maximum. On subsequent subscription requests, only limit accompanies cursor; do not repeatedly append the initial filters.

The rate-limit guide documents a standard 40-request bucket draining at two requests per second, per token. It recommends waiting at least two seconds after a 429. That guide does not document a rate-limit response header to monitor; track response codes, request volume, and the configured token allowance instead.

Webhooks and testing

Webhook delivery guidance covers subscription cancellations, creation, and order events. Acknowledge with HTTP 200 within five seconds after durable receipt. Recharge documents 20 attempts over 48 hours and eventual deletion after continued failure. Processing must tolerate repeated delivery.

For new integrations, follow the newer timestamp-bound validation reference. Read X-Recharge-Webhook-Signature and X-Recharge-Webhook-Timestamp, compute HMAC-SHA-256 over timestamp, period, and exact raw payload using the API Client Secret, then compare the digest in constant time. The documented replay tolerance is 172800 seconds. This secret differs from the access token; the legacy signature calculation is different.

The webhook guide documents a Recharge request bin and a test-subscription approach. Use synthetic data to exercise cancellation, duplicate delivery, and reactivation. A universal isolated sandbox API host was not verified in the reviewed reference; do not assume switching a hostname makes billing tests safe.

GET /subscriptions: find the working cohort

GET /subscriptions lists subscriptions with filters for status, customer, and update windows. The reference's core status values are active, cancelled, and expired; do not invent a paused status filter from a business label.

  • App: Maintain a timestamped cohort and pagination checkpoint.
  • Agent: Compare cancellation explanations across a bounded cohort.
  • Workflow: Reconcile missed callbacks through scheduled incremental retrieval.

GET /subscriptions/{id}: verify the current record

GET /subscriptions/{id} retrieves one subscription, including cancellation context and scheduling fields.

  • App: Show the current record beside the proposed action.
  • Agent: Interpret the subscriber's reason using fresh context.
  • Workflow: Recheck status immediately before executing an approved change.

GET /customers/{id}: establish subscriber identity

GET /customers/{id} retrieves the customer and documented identity fields. Recharge identity is not proof of marketing consent in another system.

  • App: Store the Recharge-to-marketing identity mapping.
  • Agent: Flag ambiguous matching evidence for review.
  • Workflow: Resolve the customer before fetching related operational context.

GET /orders: understand purchase history

GET /orders lists orders and supports customer and date filters for bounded retrieval.

  • App: Display relevant order history in the review queue.
  • Agent: Distinguish a first-order disappointment from a long-term cadence issue.
  • Workflow: Retrieve recent orders before asking for a retention recommendation.

GET /charges: separate billing from intent

GET /charges lists charges, including queued and error contexts. The reference warns that processed charges older than 90 days no longer appear in these responses.

  • App: Mark unavailable history instead of showing a misleading zero.
  • Agent: Judge whether a case needs billing support rather than promotion.
  • Workflow: Refresh charge context without issuing another payment attempt.

PUT /subscriptions/{id}: execute an authorized update

PUT /subscriptions/{id} updates an existing subscription. Treat each allowed field as an explicit authorization boundary.

  • App: Present the proposed field-level difference to a reviewer.
  • Agent: Recommend a remedy and explain its evidence.
  • Workflow: Send only approved fields, then retrieve and record the result.

POST /subscriptions/{id}/setnextcharge_date: adjust timing

POST /subscriptions/{id}/setnextcharge_date changes the next charge date. Recharge warns that matching dates for active subscriptions sharing an address can merge charges into a new charge ID.

  • App: Show the approved date and affected subscription references.
  • Agent: Assess whether the requested timing addresses the stated problem.
  • Workflow: Require approval and reconcile downstream charge identifiers afterward.

POST /webhooks: register lifecycle signals

POST /webhooks registers a callback address, topic, and payload version. Registration requires read permissions for the topic's underlying object.

  • App: Record expected registrations and their operational owner.
  • Agent: Explain a delivery gap using the available incident context.
  • Workflow: Provision approved topics and verify that expected callbacks arrive.

Recharge automation use cases on Major

Subscriber win-back with Recharge and Klaviyo

This is the published use case in the library below. Use current subscription, customer, and order reads from the API guide rather than assuming the callback contains every fact.

  • App: Store segment assignments, exclusions, event receipts, and previous outreach.
  • Agent: Interpret cancellation reasons and recommend an approved win-back segment.
  • Workflow: Trigger on cancellation, check Klaviyo consent and suppression, and emit a tracked event only for eligible subscribers.

Support-led cadence changes with Recharge and Gorgias

A subscriber saying they have too much product needs different handling from someone disputing a charge. This is a proposed pattern, not a claimed customer deployment.

  • App: Hold the support reference, requested date, evidence, and review status.
  • Agent: Read the support context and judge whether a cadence change fits the request.
  • Workflow: Use subscription retrieval and the next-charge-date operation above after approval. Read back the result and return the verified outcome to support.

Billing-exception review with Recharge and Slack

Keep billing investigation separate from promotional outreach. Use charge and order lists alongside the current subscription, with Slack as a notification destination rather than the source of billing truth.

  • App: Maintain an exception queue with owners, evidence timestamps, and resolution status.
  • Agent: Prioritize cases and draft a concise explanation of the likely issue.
  • Workflow: Schedule review, retrieve bounded charge context, and notify the assigned team. Payment retries, refunds, and concessions remain outside this read-only pattern.

Architecture: build the subscriber operations app on Major

Recharge and Klaviyo data flow through a Major workflow, judgment agent, policy gate, and stateful app

Figure 1. Recharge remains authoritative while Major holds the review process and delivery history.

Build the reusable app layer first: subscriber mappings, event receipts, recommendations, approvals, and action results belong in managed database tables. The UI should show which source facts are current, what the agent inferred, and what an authorized person approved.

The workflow handles deterministic orchestration. It verifies receipt, retrieves scoped evidence, checks duplicate keys, and constructs a bounded packet for the agent. The agent makes the judgment call, such as whether a cancellation reflects surplus inventory, price concerns, or an unresolved service problem.

Keep the policy gate outside the model's free-form answer. Code validates allowed segment names, required evidence, and approval requirements. The app stores the recommendation even when execution is blocked, so another operator can resume the case without reconstructing a conversation.

Over time, repeatable transformations become reusable software. Identity resolution rules and event-delivery checks run in code; the agent spends reasoning on cases where interpretation still matters. This is Major's reason-once, run-forever approach applied to retention operations.

A worked example with explicit arithmetic

For example, consider an illustrative team reviewing 400 cancellation cases each month. If gathering subscription history, checking marketing eligibility, and recording a decision takes six minutes per case, preparation consumes 400 times six minutes, or 40 hours monthly.

Suppose the Major app gathers the evidence automatically and the team spends two minutes reviewing each proposed segment. That is 400 times two minutes, or 13 hours and 20 minutes. Add 20 ambiguous cases requiring an extra ten minutes each, or three hours and 20 minutes. The revised total is 16 hours and 40 minutes, a difference of 23 hours and 20 minutes.

These figures are planning assumptions, not a customer result or a promise. They exclude initial implementation, incident handling, and message performance. Measure those separately before making an investment decision.

A single case moves from verified cancellation receipt to current-record retrieval, agent recommendation, eligibility check, authorized event delivery, and stored receipt. A suppressed subscriber receives no marketing event. An unresolved identity match stops in the app's review queue, with its evidence preserved for the next operator.

Governance, approvals, and failure handling

Recharge recommendations pass policy checks, with routine events separated from human-approved subscription changes

Figure 2. Preapproved routing can proceed while consequential Recharge changes wait for a person.

An agent must never independently reactivate a canceled subscription, change billing timing, issue a concession, or override marketing suppression. Give it permission to recommend; grant the execution path only the authority needed for an approved operation.

Approvals should bind to the exact subscriber, proposed fields, evidence version, and expiration time. If the underlying subscription changes before execution, stop and refresh the proposal instead of treating yesterday's approval as permanent permission.

Persist the verified callback before acknowledging it, and deduplicate both delivery receipts and business actions. Use a stable action key based on subscriber, process, and decision version so a callback replay cannot trigger another win-back journey.

For 429 responses, follow Recharge's documented waiting guidance, then use bounded backoff with jitter. After a write timeout, retrieve the current record before considering another mutation. Record failures in the app and alert an owner when retries are exhausted.

Monitor registration health because repeated delivery failures can delete webhooks. The troubleshooting guide notes that registration visibility depends on the token. Preserve actor, approval, source evidence, request outcome, and verified result without retaining unnecessary personal data.

Recharge AI Apps, Agents and Workflow Automations

This is the current core Recharge implementation guide in the library. The support and billing patterns above are additional designs to evaluate, not links to guides that have already been published. Start with the win-back guide when the owner is retention marketing and the intended output is an approved Klaviyo event.

For broader operating context, see ecommerce AI workflows, Klaviyo automation, and Gorgias support workflows. Those pages cover adjacent systems and responsibilities; they are not extra Recharge implementation entries.

Choose a process before expanding connector access. A win-back app needs marketing eligibility and assignment history. A support queue needs explicit customer authorization for a proposed subscription change. Sharing a Recharge connection does not make those permission boundaries interchangeable.

Frequently asked questions

What is Recharge AI?

Recharge AI includes native capabilities such as Remi, its dashboard assistant, and Concierge SMS for conversational subscription management. Major adds governed cross-system processes with deterministic apps, agents for judgment, and workflows for orchestration.

Does Major have a native Recharge connector?

No. Recharge connects to Major through a custom API connector with the base URL and authentication configured once by IT. Credentials stay in the connector vault, not in application code or agent prompts.

Can AI automate Recharge subscription changes?

An agent can interpret a request and recommend a change. A workflow should obtain authorization for consequential changes, recheck the current subscription, execute the approved API operation, and store its verified result in the app.

Which Recharge API scopes do retention agents need?

Start with readsubscriptions, readcustomers, and readorders for subscription, identity, order, and charge context. Add writesubscriptions only for explicitly approved subscription mutations. Webhook registration requires the read permissions appropriate to its topic.

How do Recharge webhooks handle verification and retries?

Use the recommended timestamp-bound signature and the exact raw body with the API Client Secret. Acknowledge within five seconds. Recharge documents 20 delivery attempts over 48 hours, so persist receipts and prevent duplicate actions.

Can Recharge cancellations trigger Klaviyo win-back flows?

Yes. A Major workflow can retrieve current Recharge context, ask an agent to recommend an approved segment, and send a tracked Klaviyo event after consent, suppression, and duplicate checks. Subscription cancellation does not grant marketing permission.

Sources

Start building on Major

Build a Recharge subscriber operations app with durable case history, an agent for retention judgment, and workflows that gate consequential actions. Keep subscription truth in Recharge and give operators a governed place to review the work.

About the author

Ritvij Gautam is Head of Growth at Major.

Last reviewed November 20, 2026 by Ritvij Gautam.

Frequently asked questions

What is Recharge AI?
Recharge AI includes native capabilities such as Remi, its dashboard assistant, and Concierge SMS for conversational subscription management. Major adds governed cross-system processes with deterministic apps, agents for judgment, and workflows for orchestration.
Does Major have a native Recharge connector?
No. Recharge connects to Major through a custom API connector with the base URL and authentication configured once by IT. Credentials stay in the connector vault, not in application code or agent prompts.
Can AI automate Recharge subscription changes?
An agent can interpret a request and recommend a change. A workflow should obtain authorization for consequential changes, recheck the current subscription, execute the approved API operation, and store its verified result in the app.
Which Recharge API scopes do retention agents need?
Start with read_subscriptions, read_customers, and read_orders for subscription, identity, order, and charge context. Add write_subscriptions only for explicitly approved subscription mutations. Webhook registration requires the read permissions appropriate to its topic.
How do Recharge webhooks handle verification and retries?
Use the recommended timestamp-bound signature and the exact raw body with the API Client Secret. Acknowledge within five seconds. Recharge documents 20 delivery attempts over 48 hours, so persist receipts and prevent duplicate actions.
Can Recharge cancellations trigger Klaviyo win-back flows?
Yes. A Major workflow can retrieve current Recharge context, ask an agent to recommend an approved segment, and send a tracked Klaviyo event after consent, suppression, and duplicate checks. Subscription cancellation does not grant marketing permission.