Recurly API

Name: Recurly API
Brand: Recurly API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsBilling Subscriptionsbearer20 EndpointsREST

For Agents

Create and manage subscription plans, customer accounts, invoices, and payment retries for recurring billing. Supports trials, coupons, usage add-ons, and multi-currency invoicing.

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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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, tiered, or usage-based pricing across multiple currencies

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

GET STARTED

Start building with Recurly API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Recurly API for, with concrete tasks.

★ AI Agent Subscription Management

AI agents manage Recurly subscriptions through Jentic without storing bearer tokens directly. An agent searches for 'create a subscription' via Jentic, receives the operation schema with required plan and account fields, 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', load the schema, create a subscription on a monthly plan for an existing account, then verify the subscription state is active

SaaS Subscription Billing

Bill SaaS customers on recurring schedules with support for monthly and annual plans, trial periods, and usage-based add-ons. Recurly handles proration when customers upgrade or downgrade mid-cycle, generates invoices automatically, and collects payment using stored payment methods. Failed payments trigger configurable dunning sequences 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 through automated retry schedules and customer communication workflows. Recurly retries payments at configurable intervals (e.g., day 1, 3, 5, 7) using the dunning campaign assigned to the subscription. Past-due invoices can be listed, manually collected, or written off. Revenue impact is trackable through subscription state transitions.

List all subscriptions with state past_due, retrieve the associated invoice for each, and attempt manual collection on invoices under $100

Plan and Pricing Management

Define and manage subscription plans with flexible pricing models including flat-rate, per-unit, tiered, and volume pricing. Plans support multiple currencies, setup fees, and configurable billing intervals. Coupons provide percentage or fixed-amount discounts with redemption limits and expiration dates that apply automatically at invoice generation.

Create a new plan with monthly billing at $49/month, add a usage-based add-on for API calls at $0.01 per call, then apply a 20% coupon to verify discount calculation

Key Endpoints

20 endpoints — jentic publishes the only available openapi specification for recurly api, keeping it validated and agent-ready.

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Recurly Bearer API keys are stored encrypted in the Jentic MAXsystem vault. Agents receive scoped access tokens — the raw private key never enters the agent's context window.

Intent-based discovery

Agents search by intent (e.g., 'create a subscription' or 'list past-due invoices') and Jentic returns the matching Recurly operation with its full request schema, so the agent constructs the correct payload without reading API docs.

Time to first call

Direct Recurly integration: 2-4 days for auth, subscription creation flow, webhook setup, and dunning configuration. Through Jentic: under 1 hour — search, load schema, execute with credential isolation.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Stripe API

Full-stack payment platform with built-in subscription billing and broader payment method support

Choose Stripe when you need payment processing and subscriptions in one platform, or when broad payment method support (wallets, BNPL) is important

Alternative

Paddle API

Merchant-of-record subscription platform handling tax and compliance automatically

Choose Paddle when you need a merchant-of-record model where the platform handles sales tax, VAT collection, and remittance obligations

Alternative

PayPal Subscriptions API

PayPal-native recurring billing for subscribers with PayPal accounts

Choose PayPal Subscriptions when your customers prefer paying with their PayPal balance and you want buyer protection for recurring payments

Complementary

Stripe API

Use Stripe as the payment gateway underneath Recurly's subscription management

Use Stripe as the payment processor while Recurly handles subscription logic, dunning, and revenue recognition on top

FAQs

Specific to using Recurly API through Jentic.

Why is there no official OpenAPI spec for Recurly API?

Recurly does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Recurly API via structured tooling. It is validated against the live API and kept up to date. Sign up at https://app.jentic.com/sign-up to get started.

What authentication does the Recurly API use?

The Recurly API uses Bearer token authentication. Pass your private API key in the Authorization header as 'Bearer {api_key}'. Keys are site-specific and can be generated in the Recurly admin console. Through Jentic, your Recurly API key is stored encrypted in the MAXsystem vault — agents authenticate without seeing the raw token.

Can I handle failed payment retries with the Recurly API?

Yes. Recurly's dunning system automatically retries failed payments on a configurable schedule. You can list past-due subscriptions via GET /subscriptions filtering by state, retrieve their invoices via GET /invoices/{invoice_id}, and trigger manual collection attempts. The subscription state transitions through active → past_due → canceled based on dunning outcomes.

What are the rate limits for the Recurly API?

Recurly applies rate limits of 2000 requests per minute per site for API v3. Rate limit headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset) are included in every response. If exceeded, the API returns HTTP 429 with a Retry-After header indicating when to retry.

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. Required fields are plan_code (identifying the billing plan) and account (with account_code and billing_info). Optional fields include coupon_codes, starts_at for future-dated subscriptions, and trial_ends_at. Jentic loads the full schema automatically. Sign up at https://app.jentic.com/sign-up to get started.

Does the Recurly API support multi-currency billing?

Yes. Plans can be configured with pricing in multiple currencies. When creating a subscription, the currency is determined by the account's billing info or can be explicitly set. Invoices are generated in the subscription's currency with appropriate tax calculations. The GET /plans endpoint returns all configured currency amounts for each plan.

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.