ChartMogul API
Browse all Chartmogul APIs★ Only Publicly Available OpenAPI DocumentAnalyticsBusiness Intelligencebasic24 EndpointsREST
For Agents
Read SaaS metrics and write customers, plans, and invoices to ChartMogul. Basic-auth REST API with 24 endpoints covering full subscription-analytics ingestion and reporting.
Use for: I need to import invoices into ChartMogul from my billing system, Create a new customer in ChartMogul, Get the latest MRR from ChartMogul, Search for a ChartMogul customer by external_id
Not supported: Does not handle payment processing, dunning, or invoice generation for end customers — use for importing subscription data into ChartMogul and reading SaaS metrics only.
Jentic publishes the only available OpenAPI specification for ChartMogul API, keeping it validated and agent-ready. ChartMogul ingests subscription billing data and exposes the canonical SaaS metrics — MRR, ARR, ARPA, ASP, customer churn, MRR churn, LTV, and customer count. This main surface adds write operations for customers, contacts, plans, and invoices alongside the metric reads, making it suitable for both reporting and bidirectional billing-data sync. It uses HTTP basic authentication with the API key as the username.
Install Jentic One Beta
Connect the ChartMogul API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ChartMogul 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
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 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 ChartMogul API.
Create, update, list, search, and delete customer records via /customers and /customers/{customerUuid}
Maintain customer contacts via the /customers/{customerUuid}/contacts endpoints
Register and list billing data sources with POST /data_sources and GET /data_sources
Import plans and invoices into ChartMogul via POST /plans and POST /invoices
Retrieve MRR, ARR, ARPA, ASP, customer count, customer churn rate, MRR churn rate, and LTV from /metrics/*
List subscriptions for a given customer via GET /customers/{customerUuid}/subscriptions
Trigger an activities export with POST /activities-export for downstream analysis
Use Cases
Patterns agents use ChartMogul API for, with concrete tasks.
★ Push subscription data from a custom billing system
Custom in-house billing systems can post customers, plans, and invoices into ChartMogul so that ChartMogul takes over MRR/ARR/churn calculation. Use POST /data_sources to register the system, then POST /customers, POST /plans, and POST /invoices to load the data. From there, the metric endpoints return the same numbers the ChartMogul UI shows.
Create a data source called 'Internal Billing', then create a customer with email user@example.com, create a $99/month plan, and import an invoice for that customer; verify by reading the customer back
Build a daily SaaS metrics digest
Pull MRR, ARR, ARPA, ASP, customer count, customer churn rate, MRR churn rate, and LTV from /metrics/* endpoints once per day and post a digest into a Slack channel. Because all eight metrics share the same query-parameter shape, an agent can fetch them in a tight loop and emit a consistent table without per-metric special-casing.
Call /metrics/mrr, /metrics/arr, /metrics/arpa, /metrics/asp, /metrics/customer-count, /metrics/customer-churn-rate, /metrics/mrr-churn-rate, and /metrics/ltv for yesterday and emit a one-line digest
Reconcile customer records between billing and CRM
Use GET /customers/search to look up a ChartMogul customer by external_id or email, then add or update contacts via /customers/{customerUuid}/contacts. This keeps the contact roster in ChartMogul aligned with the CRM source of truth, which matters when running churn-risk reports tied to specific stakeholders.
Search ChartMogul for a customer with external_id 'acme-1234', then create a contact with email cfo@acme.com and role 'CFO' on that customer
Answer SaaS-metric questions inside an AI agent
An AI agent uses Jentic to discover ChartMogul's metric endpoints and customer endpoints, loads their schemas, and answers natural-language questions like 'what is current MRR?' or 'how many customers churned last month?' without bespoke code. Jentic's vault holds the basic-auth credential so the agent never sees the raw API key.
Search Jentic for 'get chartmogul mrr churn', load the operation schema, retrieve MRR churn rate for the last 90 days, and report the trend
Key Endpoints
24 endpoints — jentic publishes the only available openapi specification for chartmogul api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/customers
Create a customer
GET
/customers/search
Search customers by email or external_id
POST
/invoices
Import invoices
POST
/plans
Create a plan
GET
/metrics/mrr
Get MRR
GET
/metrics/mrr-churn-rate
Get MRR churn rate
GET
/metrics/ltv
Get LTV
POST
/activities-export
Create an activities export
POST
/customers
Create a customer
GET
/customers/search
Search customers by email or external_id
POST
/invoices
Import invoices
POST
/plans
Create a plan
GET
/metrics/mrr
Get MRR
GET
/metrics/mrr-churn-rate
Get MRR churn rate
GET
/metrics/ltv
Get LTV
POST
/activities-export
Create an activities export
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
ChartMogul API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive a scoped basic-auth credential at execution time — the raw key never enters the agent's prompt context.
Intent-based discovery
Agents search by intent (e.g., 'import invoices to chartmogul' or 'get chartmogul mrr') and Jentic returns the matching ChartMogul operations with their input schemas.
Time to first call
Direct ChartMogul integration: 1 day to wire up basic auth, model the customer/plan/invoice import order, and parse the metric response shape. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Stripe API
Stripe is a common upstream billing source for ChartMogul.
Use Stripe to read raw payments and subscriptions; use ChartMogul to read pre-computed SaaS metrics derived from those payments.
FAQs
Specific to using ChartMogul API through Jentic.
Why is there no official OpenAPI spec for ChartMogul API?
ChartMogul does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ChartMogul 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 ChartMogul API use?
The ChartMogul API uses HTTP basic authentication. Send your API key as the username and an empty password against api.chartmogul.com/v1. Through Jentic, the key is stored in the encrypted MAXsystem vault and injected at execution time so it never enters the agent's prompt.
Can I import invoices into ChartMogul with this API?
Yes. POST /invoices imports a batch of invoices for a customer. Before that, register the data source with POST /data_sources, create the customer with POST /customers, and create the relevant plan with POST /plans so each invoice can reference real foreign keys.
How do I look up a ChartMogul customer by external_id?
Call GET /customers/search with the data_source_uuid and external_id query parameters. It returns the matching customer record so you can chain into /customers/{customerUuid} or /customers/{customerUuid}/subscriptions for follow-up calls.
How do I get ChartMogul MRR through Jentic?
Run pip install jentic, set JENTIC_AGENT_API_KEY, then search 'get chartmogul mrr'. Jentic returns GET /metrics/mrr with its query parameter schema. Supply start-date and end-date and execute — the agent gets the MRR series without browsing docs.
Are there documented rate limits for the ChartMogul API?
The OpenAPI spec does not declare rate-limit headers or per-key quotas. ChartMogul's import-heavy endpoints (POST /invoices, POST /activities-export) are usually subject to soft limits — back off on 429 responses and check any RateLimit headers the live service returns.
GET STARTED