Recurly API
★ Only Publicly Available OpenAPI DocumentPaymentsBilling Subscriptionsbasic20 EndpointsREST
For Agents
Create and manage subscription plans, customer accounts, invoices, and payment retries for recurring billing. Supports trials, coupons, and usage-based add-ons.
Use for: I need to create a new subscription plan with monthly billing, Set up a customer account with billing information, Check whether a subscription payment has failed, List all active subscriptions for a specific account
Not supported: Does not handle one-time payment checkout, marketplace payouts, or in-person POS transactions - use for recurring subscription billing and invoicing only.
Manage subscription billing lifecycle including plan creation, customer accounts, recurring invoicing, and dunning for failed payments. The API handles subscription state transitions (active, canceled, expired, failed, future, paused). Recurly publishes its own OpenAPI document for the v2021-02-25 API on its developer site, covering 197 operations; this Jentic entry is a curated 20-operation subset of it covering the core subscription, account, invoice, plan, item, transaction, and coupon calls.
Install Jentic One Beta
Connect the Recurly API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Recurly API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frecurly.com%2Frecurly" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frecurly.com%2Frecurly" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Recurly API.
Create subscription plans with fixed or ramp pricing models, setup fees, and tiered or usage-based add-ons
Manage customer accounts with billing info, shipping addresses, and payment method tokens
Generate and collect invoices automatically at each billing cycle with line items and tax
Create discount coupons and list the coupons configured on the site
Handle failed payment retries through the dunning campaign assigned to a subscription
Cancel subscriptions and reactivate canceled ones before they expire
Use Cases
Patterns agents use Recurly API for, with concrete tasks.
★ AI Agent Subscription Management
AI agents manage Recurly subscriptions through Jentic without storing the API key directly. An agent searches for 'create a subscription' via Jentic, is routed to the POST /subscriptions operation, and executes the call with credential isolation. Subscription status checks, cancellations, and reactivations follow the same intent-based discovery pattern.
Search Jentic for 'create a Recurly subscription', call POST /subscriptions for an existing account on a monthly plan, then confirm the state is active with GET /subscriptions/{subscription_id}
SaaS Subscription Billing
Bill SaaS customers on recurring schedules with support for monthly and annual plans, trial periods, and usage-based add-ons. Recurly generates invoices automatically and collects payment using stored payment methods. Failed payments trigger the dunning campaign assigned to the subscription, with retry attempts and customer notifications.
Create a customer account with billing info, subscribe them to a monthly plan with a 14-day trial, then retrieve the first invoice to confirm it shows zero amount during trial
Dunning and Payment Recovery
Recover failed subscription payments using the dunning campaign assigned to the subscription. Recurly's entry Starter plan includes one dunning campaign and multiple campaigns are an All-Access plan feature, so check your own plan before relying on more than one. past_due is an invoice state rather than a subscription state, so recovery work is driven from invoices: list them, retrieve the ones in state past_due, and collect or write them off.
List invoices with GET /invoices, pick out the ones whose state is past_due, retrieve each with GET /invoices/{invoice_id}, and report the ones under $100 for collection
Plan and Pricing Management
Define and manage subscription plans with a fixed or ramp pricing model, setup fees, and billing intervals in days or months. Add-on pricing models are flat, tiered, stairstep, or volume. Multicurrency plan pricing is an All-Access plan feature at Recurly, so confirm your plan includes it before configuring per-currency amounts. Discount coupons can be created and listed here; attaching a coupon to a subscription is not one of this entry's 20 operations.
Create a plan with POST /plans set to a monthly interval at $49, read it back with GET /plans/{plan_id} to confirm the interval and amount, then create a 20% discount coupon with POST /coupons
Key Endpoints
20 endpoints — manage subscription billing lifecycle including plan creation, customer accounts, recurring invoicing, and dunning for failed payments.
METHOD
PATH
DESCRIPTION
POST
/subscriptions
Create a new subscription for an account
GET
/subscriptions/{subscription_id}
Retrieve subscription details
PUT
/subscriptions/{subscription_id}/cancel
Cancel a subscription
PUT
/subscriptions/{subscription_id}/reactivate
Reactivate a canceled subscription
GET
/accounts
List all customer accounts
GET
/invoices/{invoice_id}
Retrieve invoice details
GET
/plans
List all billing plans
POST
/accounts
Create a new customer account
POST
/subscriptions
Create a new subscription for an account
GET
/subscriptions/{subscription_id}
Retrieve subscription details
PUT
/subscriptions/{subscription_id}/cancel
Cancel a subscription
PUT
/subscriptions/{subscription_id}/reactivate
Reactivate a canceled subscription
GET
/accounts
List all customer accounts
GET
/invoices/{invoice_id}
Retrieve invoice details
GET
/plans
List all billing plans
POST
/accounts
Create a new customer account
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Recurly API by hand means handling its HTTP Basic auth with the API key as the username, sending an Accept header that names the API version on every call, pointing at the right regional host, and managing requests yourself. Through Jentic you install once, import the Recurly API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Recurly puts the subscription id in the URL path (/subscriptions/{subscription_id}), so a rule can pin your agent to specific subscriptions. You choose the operations it may call, so state changes like cancelling a subscription are only included if you add them.
Credential isolation
Your Recurly API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a subscription' or 'look up an invoice', and Jentic returns the matching Recurly operation so the agent calls the right endpoint without hunting through the reference docs for it. Request payloads still come from Recurly's own OpenAPI document, which this 20-operation entry does not reproduce.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Recurly API through Jentic.
How does this Jentic entry relate to Recurly's own OpenAPI spec?
Recurly publishes an OpenAPI 3.0 document for the v2021-02-25 API at `https://recurly.com/developers/api/spec/v2021-02-25.yaml`, describing 197 operations. This Jentic entry is a curated 20-operation subset of that surface, covering the core subscription, account, invoice, plan, item, transaction, and coupon calls that agents ask for most. Use Recurly's document when you need an operation outside those 20. Run either through Jentic One, the self-hosted execution layer.
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.
GET STARTED