List subscriptions with the Recharge API

Lists the subscriptions of the store with customer, address, product, quantity, price, frequency, status and next_charge_scheduled_at. Up to 250 per page: pass the next_cursor of the response as cursor to read the next page.

Identifier
recharge_list_subscriptions

The request

POST https://connect.reportei.com/api/tools/recharge_list_subscriptions/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "status": "active"
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
statusstringNoOnly subscriptions in this status.Values: active, cancelled, expired
customer_idintegerNoOnly subscriptions of this customer, the id from List customers.
address_idintegerNoOnly subscriptions of this address, from the addresses of Get customer.
external_variant_idstringNoOnly subscriptions of this product variant: the variant id of the store platform, the value of external_variant_id.ecommerce in List subscriptions.
idsstringNoComma-separated ids of subscriptions from List subscriptions.
created_at_minstringNoOnly subscriptions created after this date, as YYYY-MM-DD.
created_at_maxstringNoOnly subscriptions created before this date, as YYYY-MM-DD.
updated_at_minstringNoOnly subscriptions updated after this date, as YYYY-MM-DD. With status cancelled, it finds recent cancellations.
updated_at_maxstringNoOnly subscriptions updated before this date, as YYYY-MM-DD.
limitintegerNoSubscriptions per page, up to 250. The default is 50.
cursorstringNoThe next_cursor or previous_cursor of the previous response.

Supported connections

Your customer connects their Recharge account once, with one of the modes below. The same connection serves every tool of the toolkit.

API key

Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/recharge_list_subscriptions. It becomes your agent's tool definition with no conversion.

Other Recharge tools

See all 12 tools

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.