Billsby API

Name: Billsby API API
Brand: Billsby API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsBilling SubscriptionsapiKey58 EndpointsREST

For Agents

Run a full subscription billing lifecycle — customers, plans, invoices, refunds, and add-ons — through the Billsby subscription billing platform.

Quickstart

Get started with Billsby API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a Billsby subscription"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Billsby API API.

Manage subscribers end-to-end: create customers, attach subscriptions, change plans, and cancel

Charge a one-time fee on top of a subscription via POST /customers/{customerId}/charge

Refund, reattempt, write off, or mark invoices as paid offline for accounts-receivable workflows

Operate metered subscriptions by reading and updating counters per subscription

GET STARTED

Start building with Billsby API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Billsby API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Billsby API, keeping it validated and agent-ready. The Billsby API is the public interface to the Billsby subscription billing platform, exposing 58 endpoints to manage customers, subscriptions, invoices, credit notes, products, plans, add-ons, allowances, and custom fields. It supports the full subscription lifecycle: creating customers and subscriptions, changing plans, refunding or writing off invoices, tracking counters and feature tags, and retrieving event logs. The base URL is templated by company domain, and authentication is by API key in the apikey header.

Use Cases

Patterns agents use Billsby API API for, with concrete tasks.

★ SaaS Subscription Lifecycle Automation

SaaS businesses need an end-to-end subscription engine — sign-up, plan upgrades, renewals, cancellations. The Billsby API exposes POST /subscriptions to create a new customer with subscription, PUT /subscriptions/{subscriptionId}/changeplan for upgrades, and DELETE /subscriptions/{subscriptionId} to cancel. Combined with /invoices and /creditnotes, it covers the full revenue cycle without a separate invoicing tool. Setup is typically three to five days for a first-time integration.

Create a new customer with a subscription on plan ID 1234 via POST /subscriptions, then change the plan to 5678 a week later via PUT /subscriptions/{subscriptionId}/changeplan.

Metered Usage Billing

Usage-based pricing requires tracking counters per subscriber, with billing reflecting accumulated usage. The Billsby API exposes GET and POST on /subscriptions/{subscriptionId}/counter for reading and updating counters, and /allowances for plan-level inclusion limits. Together these support the standard pattern: increment the counter as usage accrues, and Billsby reflects the overage on the next invoice. Setup is typically two days plus testing.

For subscription ID 4567, increment the counter by 250 via POST /subscriptions/{subscriptionId}/counter, then verify via GET that the new value is reflected.

Accounts Receivable and Refunds

Finance teams need to refund overcharged invoices, reattempt failed payments, and reconcile invoices paid offline. The Billsby API supports POST /invoices/{invoiceId}/refund, PUT /invoices/{invoiceId}/reattempt, PUT /invoices/{invoiceId}/paidoffline, and PUT /invoices/{invoiceId}/writeoff in one place, which avoids spreading these flows across multiple tools. Setup is one to two days for a finance ops integration.

Refund invoice ID 88991 in full via POST /invoices/{invoiceId}/refund, then verify via GET /invoices/{invoiceId} that the status reflects the refund.

AI Agent Subscription Manager via Jentic

A customer-success AI assistant can change plans, refund invoices, and look up event logs from natural-language requests routed through Jentic. The Billsby API key sits in the Jentic vault, so the agent never touches the raw secret. Search-load-execute through Jentic gets the agent live in under an hour, versus several days for direct integration.

Search Jentic for 'cancel a Billsby subscription', load the DELETE /subscriptions/{subscriptionId} schema, and execute it for the customer's subscription ID.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/subscriptions

Create a customer with a new subscription

DELETE

/subscriptions/{subscriptionId}

Cancel a subscription

PUT

/subscriptions/{subscriptionId}/changeplan

Change a subscription's plan

POST

/customers/{customerId}/charge

Create a one-time charge on a customer

POST

/invoices/{invoiceId}/refund

Refund an invoice

PUT

/invoices/{invoiceId}/reattempt

Reattempt payment on a failed invoice

POST

/subscriptions/{subscriptionId}/counter

Update a metered usage counter

GET

/subscriptions/{subscriptionId}/eventlogs

Retrieve a subscription's event log

POST

/subscriptions

Create a customer with a new subscription

DELETE

/subscriptions/{subscriptionId}

Cancel a subscription

PUT

/subscriptions/{subscriptionId}/changeplan

Change a subscription's plan

POST

/customers/{customerId}/charge

Create a one-time charge on a customer

POST

/invoices/{invoiceId}/refund

Refund an invoice

Why though Jentic?

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

Credential isolation

Billsby API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — the raw apikey header value never enters the agent's context or logs.

Intent-based discovery

Agents search by intent (e.g., 'cancel a Billsby subscription') and Jentic returns the matching Billsby operation with its input schema, so the agent can call the right endpoint without browsing third-party docs.

Time to first call

Direct Billsby integration: 3-5 days for a full subscription lifecycle including invoice handling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Stripe

Global payments and subscription billing platform

Choose Stripe for global payment processing alongside billing; choose Billsby for a subscription-first product with simpler plan and add-on modelling.

Alternative

Recurly

Subscription billing platform with comparable lifecycle features

Choose Recurly for enterprise-scale subscription billing with deeper revenue recognition; choose Billsby for SMB-friendly setup.

Alternative

Paddle

Merchant-of-record subscription billing platform

Choose Paddle to offload sales-tax compliance via the merchant-of-record model; choose Billsby when you remain the merchant of record.

Alternative

Chargify (Maxio)

Subscription billing with strong support for B2B SaaS metering

Choose Chargify for complex B2B metering and revenue events; choose Billsby for a simpler subscription billing surface.

FAQs

Specific to using Billsby API API through Jentic.

Why is there no official OpenAPI spec for Billsby API?

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

What authentication does the Billsby API use?

The Billsby API uses an API key passed in the apikey header. You generate the key in the Billsby admin under Settings > Configuration > API keys and webhooks. When called via Jentic, the key is held in the MAXsystem vault so the raw apikey value never reaches the agent's context.

Can I change a customer's plan through the Billsby API?

Yes. PUT /subscriptions/{subscriptionId}/changeplan moves an existing subscription to a different plan, and PUT /subscriptions/{subscriptionId}/renewaldate adjusts the next renewal date. These two endpoints cover most upgrade and downgrade flows without needing to recreate the subscription.

What are the rate limits for the Billsby API?

The OpenAPI spec does not declare explicit numeric rate limits. Billsby's standard practice is to throttle abusive callers and return 429 responses when limits are exceeded. The Jentic SDK retries on 429 with back-off, so high-volume jobs do not have to handle this manually.

How do I refund an invoice through Jentic?

Search Jentic for 'refund a Billsby invoice', which surfaces POST /invoices/{invoiceId}/refund. Load the schema, supply the invoice ID and refund amount, and execute. The Python flow is: pip install jentic, then await client.search, await client.load, await client.execute.

Does the Billsby API support metered or usage-based billing?

Yes. GET and POST on /subscriptions/{subscriptionId}/counter let you read and update usage counters per subscription, and /allowances exposes the plan-level inclusions that determine when overage billing applies.