ChargeOver API

Name: ChargeOver API
Brand: ChargeOver API
Availability: InStock

✓ Official Vendor SpecPaymentsBilling Subscriptionsbasic31 EndpointsREST

For Agents

Manage customers, invoices, subscriptions, and transactions for a recurring billing platform, including action endpoints to suspend, cancel, void, or charge. Useful for finance ops and customer success agents.

Install Jentic One Beta

Connect the ChargeOver API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ChargeOver 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 ChargeOver API.

Create, retrieve, update, and deactivate customer records via the /customers endpoints, including emailing and inactive flagging through action parameters

Issue and manage invoices with /invoices, including void, late-fee application, email, payment capture, and PDF retrieval

Run the subscription lifecycle through /subscriptions: suspend, unsuspend, cancel, uncancel, and upgrade-downgrade via action parameters

GET STARTED

Start building with ChargeOver API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use ChargeOver API for, with concrete tasks.

★ Recurring SaaS Billing Operations

B2B SaaS finance teams use ChargeOver to manage subscription lifecycles for customers, including suspending past-due accounts and uncancelling reactivations. The /subscriptions endpoints with action=suspend, unsuspend, cancel, uncancel, and upgrade-downgrade let an integrator implement dunning, win-back, and plan-change workflows from a single namespace.

POST /subscriptions/{subscription_id}?action=suspend for any subscription with an unpaid invoice older than 30 days

Invoice Issuance and Collection

Finance teams create one-off and scheduled invoices through POST /invoices, then drive collection via the action endpoints: action=email to send the invoice, action=late-fee to add penalties, action=pay to capture payment against a stored method, and action=void to nullify a mistakenly issued invoice. GET /invoices/{invoice_id}/pdf returns the formatted invoice for downstream archiving.

POST /invoices with the line items, then POST /invoices/{invoice_id}?action=email to deliver it to the customer

Customer Lifecycle Management

Customer success and finance ops teams keep ChargeOver in sync with their CRM by creating customers via POST /customers and toggling active status through the action=active and action=inactive variants. Listing /customers with filters supports reconciliation against the CRM and pulling /customers/{customer_id} returns the full billing record for support contexts.

POST /customers/{customer_id}?action=inactive when the matching CRM record is marked churned

Agent-Driven Billing Operations via Jentic

An AI agent given an instruction like 'cancel any subscription whose customer has not paid in 60 days' can resolve the workflow through Jentic. It searches Jentic for the subscription cancel operation, identifies past-due records via /invoices, and posts /subscriptions/{id}?action=cancel — all while the API key stays in the MAXsystem vault.

Search Jentic for 'cancel a subscription', identify past-due subscriptions, and POST /subscriptions/{id}?action=cancel for each

Key Endpoints

31 endpoints — chargeover is a recurring and subscription billing platform for b2b and saas businesses.

METHOD

PATH

DESCRIPTION

POST

/customers

Create a customer record

POST

/invoices

Create an invoice

POST

/invoices/{invoice_id}?action=pay

Capture payment against an invoice

POST

/subscriptions

Create a subscription

POST

/subscriptions/{subscription_id}?action=cancel

Cancel a subscription

POST

/subscriptions/{subscription_id}?action=upgrade-downgrade

Change a subscription plan

POST

/transactions/{transaction_id}?action=void

Void a transaction

POST

/customers

Create a customer record

POST

/invoices

Create an invoice

POST

/invoices/{invoice_id}?action=pay

Capture payment against an invoice

POST

/subscriptions

Create a subscription

POST

/subscriptions/{subscription_id}?action=cancel

Cancel a subscription

Why Jentic?

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

Credential isolation

ChargeOver uses HTTP Basic over TLS. Jentic stores the credential encrypted in the MAXsystem vault and the agent only sees a scoped execution token, so the credential never appears in agent prompts, logs, or repos.

Intent-based discovery

Agents query Jentic with intents like 'cancel a subscription' or 'create an invoice', and Jentic returns the matching ChargeOver operation with the action query parameter pre-resolved.

Time to first call

Direct ChargeOver integration: 3-5 days to model customers, subscriptions, invoices, and the action-style endpoints. Through Jentic: under an hour — search, load, execute against the right resource ID.

FAQs

Specific to using ChargeOver API through Jentic.

What authentication does the ChargeOver API use?

ChargeOver uses HTTP Basic authentication over TLS, with credentials issued from your account settings. Through Jentic, the credential is held encrypted in the MAXsystem vault and the agent only sees a scoped execution token rather than the raw username and password pair.

Can I cancel a subscription through the ChargeOver API?

Yes. POST /subscriptions/{subscription_id}?action=cancel cancels the subscription. Use action=uncancel to reactivate before the term ends, action=suspend to pause without cancelling, and action=upgrade-downgrade to change the plan.

How do I email an invoice with the ChargeOver API?

Call POST /invoices/{invoice_id}?action=email. ChargeOver renders the invoice and sends it to the on-file email for the customer. The same pattern (action=email) works for /customers/{customer_id}?action=email when sending an account-level message.

What are the rate limits for the ChargeOver API?

ChargeOver does not publish a fixed public rate limit; production limits depend on your plan. Implement exponential backoff on HTTP 429 responses and prefer batched reads (filtering /customers or /invoices) over per-record polling.

How do I capture payment against an invoice through Jentic?

Install jentic with pip install jentic, search for 'capture payment on an invoice', load the schema for POST /invoices/{invoice_id}?action=pay, and execute. Sign up at https://app.jentic.com/sign-up for an agent API key.

Does the ChargeOver API expose invoice PDFs?

Yes. GET /invoices/{invoice_id}/pdf returns the PDF representation of the invoice, suitable for archiving in your document store or attaching to outbound customer communications.

ChargeOver API

Connect the ChargeOver API to your agent

Capabilities

Start building with ChargeOver API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs