Recurly API

What authentication does the Recurly API use?

HTTP Basic, not Bearer. Recurly's own spec says to 'Enter the API key as the username and set the password to an empty string'. Keys are site-specific and are managed on the API Credentials page in the Recurly admin console. Every request must also name an API version, for example the header 'Accept: application/vnd.recurly.v2021-02-25' - Recurly's spec warns that specifying a version is required to get a successful response. Sites in the EU region are served from https://v3.eu.recurly.com instead of https://v3.recurly.com. Through Jentic, your Recurly API key is stored encrypted in your Jentic One instance and agents authenticate without seeing the raw key.

Can I handle failed payment retries with the Recurly API?

Yes. Recurly retries failed payments using the dunning campaign assigned to the subscription. Note that past_due is an invoice state, not a subscription state: the invoice states are open, pending, processing, past_due, paid, closed, failed, and voided, while subscription states are active, canceled, expired, failed, future, and paused. So find recovery work through invoices - list them with GET /invoices and read each invoice's state, then pull the detail with GET /invoices/{invoice_id}. On dunning depth, Recurly's entry Starter plan includes one dunning campaign and multiple campaigns are an All-Access plan feature, so check your plan.

What are the rate limits for the Recurly API?

By default Recurly gives new sites 1,000 requests per minute on production sites, where only GET requests count towards the limit, and 400 requests per minute on sandbox sites, where all requests count. The limit is calculated over a sliding 5 minute window. Exceeding it returns HTTP 429 Too Many Requests. The applicable limit is reported in the X-RateLimit-Limit header, the remaining allowance in X-RateLimit-Remaining, and the reset time as a UNIX timestamp in X-RateLimit-Reset.

How do I create a subscription through the Recurly API via Jentic?

Search Jentic for 'create a Recurly subscription' to find the POST /subscriptions operation, then run it through Jentic One, the self-hosted execution layer. This 20-operation entry describes the operation and its responses but carries no request body schema, so build the payload from Recurly's own OpenAPI document, whose SubscriptionCreate schema requires three fields: plan_code (or plan_id), currency as a 3-letter ISO 4217 code, and account.

Does the Recurly API support multi-currency billing?

On the plans that include it. Recurly lists Multicurrency under its All-Access tier; the Starter tier's included list does not name it, so confirm your own Recurly plan before building on it. Where it is enabled, a plan on the fixed pricing model carries a currencies block with an amount per currency, returned by GET /plans, and every subscription names its own currency as a 3-letter ISO 4217 code at creation.

Can I cancel and reactivate subscriptions through the API?

Yes. PUT /subscriptions/{subscription_id}/cancel cancels a subscription at the end of the current billing period (the subscriber retains access until period end). PUT /subscriptions/{subscription_id}/reactivate restores a canceled subscription before it expires. Both endpoints return the updated subscription object with the new state.

Is there a Recurly MCP server?

You don't need an MCP server to give your agent Recurly. Jentic connects it directly from the API Directory: import the Recurly API, store your API key once in your own Jentic One instance, and your agent calls the operations you allow. Nothing extra to run alongside your agent, and no tool definitions sitting in its context when it is doing something else.

Can I limit what my agent is allowed to do with the Recurly API?

Yes. Because you run Jentic One yourself, your own rules decide which Recurly operations the agent may call and which credentials it may use, so you can allow read-only calls like GET /invoices/{invoice_id} while withholding state changes such as PUT /subscriptions/{subscription_id}/cancel or POST /subscriptions. Since Recurly puts the subscription id in the URL path, a rule can also pin the agent to specific subscriptions rather than the whole account. Cancellation and reactivation are only available to the agent if you explicitly add those operations.