Monto API
Agent-ready OpenAPI document · curated by JenticFinanceAccountingapiKey37 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Read normalised accounting data - companies, accounts, journals, customer invoices, and financial statements - across ERPs through Monto's unified API.
Use for: List all companies my Monto subscription has access to, Pull the latest balance sheet for company c_42, Get all customer invoices for the last quarter, Find unreconciled accounts in a company's chart of accounts
Not supported: Does not write journal entries or post invoices back into the source ERP, and does not handle bank-feed ingestion - use Monto for read-only unified accounting data only.
Jentic publishes the only available OpenAPI specification for Monto API, keeping it validated and agent-ready. Monto provides a unified accounting API across underlying ERP and accounting integrations such as QuickBooks, Xero, and others, exposing companies, accounts, journals, customer invoices, balance sheets, income statements, and account transactions through a single surface. The 37-endpoint API also includes data quality signals (consistency, liquidity), metrics, and a connection lifecycle for adding new integrations to a company. Authentication is an API key in the Authorization header.
Install Jentic One Beta
Connect the Monto API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Monto 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%2Fmonto.ai%2Fmonto" | 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%2Fmonto.ai%2Fmonto" | 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 Monto API.
Connect a company to QuickBooks, Xero, or another supported ERP via /integrations and /subscriptions
List the chart of accounts and account transactions across every connected accounting system in one schema
Pull standardised balance sheets and income statements per company without integration-specific quirks
Read customer invoices and their payments to drive AR analytics and dunning workflows
Surface data quality signals like consistency and liquidity to flag closing or reconciliation gaps
Compute portfolio metrics across companies for fund or accountant reporting
Use Cases
Patterns agents use Monto API for, with concrete tasks.
★ Lender Underwriting from Live Books
A lender uses Monto to pull a borrower's accounts, journals, customer invoices, balance sheet, and income statement directly from QuickBooks or Xero through one API. The data is normalised across providers, so the underwriting model does not need ERP-specific adapters and can score the company on liquidity and consistency signals returned by Monto.
Pull the latest balance sheet, income statement, and consistency score for company c_42 and return the current ratio plus the most recent monthly net income.
Accounts Receivable Automation
Finance ops uses Monto's customer invoice and customer invoice payment endpoints to build dashboards and dunning workflows that span every entity in the group. Because the data is unified, the same logic works whether a subsidiary uses QuickBooks Online or Xero, removing the need for parallel codepaths per ERP.
List customer invoices over 30 days past due across every Monto company and group totals by customer.
Embedded Bookkeeping Insights
A SaaS app that serves SMBs embeds Monto to read each customer's accounting data and surface insights - runway, customer concentration, expense growth - without forcing the SMB to export CSVs. The /companies, /metrics, and /balance-sheet endpoints provide enough surface for a useful insights screen built on top of normalised numbers.
For company c_77 compute monthly burn over the last six months and project the runway given current cash on the latest balance sheet.
AI Agent Financial Analysis
An analyst agent uses Jentic to discover Monto's accounting endpoints and run multi-company queries with vault-stored API keys. Because Monto does not publish a public OpenAPI spec, Jentic's spec is the only structured way for an agent to call the unified accounting API without scraping the developer portal.
Search Jentic for 'pull a company's income statement', load the Monto income statement schema, and execute it for company c_42 over the trailing twelve months.
Key Endpoints
37 endpoints — jentic publishes the only available openapi specification for monto api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/integrations
List supported ERP integrations
GET
/companies
List companies in the subscription
POST
/companies
Create a company
GET
/companies/{company-uuid}/customer-invoices
List customer invoices for a company
GET
/subscriptions
List Monto subscriptions
POST
/subscriptions
Create a subscription
DELETE
/companies/{company-uuid}
Delete a company
GET
/integrations
List supported ERP integrations
GET
/companies
List companies in the subscription
POST
/companies
Create a company
GET
/companies/{company-uuid}/customer-invoices
List customer invoices for a company
GET
/subscriptions
List Monto subscriptions
POST
/subscriptions
Create a subscription
DELETE
/companies/{company-uuid}
Delete a company
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Monto by hand means setting up its API key in the Authorization header, picking the production or test host, and threading the company UUID through each unified-accounting call. Through Jentic you install once, import the Monto API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Monto puts the company id in the URL path (/companies/{company-uuid}/...), so a rule can pin your agent to one company: it can read that company's customer invoices and nothing else. You choose the operations it may call, so a destructive one like deleting a company is not included unless you add it.
Credential isolation
Your Monto API key is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'pull a company's customer invoices' or 'list connected integrations', and Jentic returns the matching Monto operation with its input schema, including the company UUID parameter, so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Stripe API
Read collected payments from Stripe alongside ERP-side invoices in Monto
Pair when revenue is collected on Stripe but recognised in QuickBooks or Xero accessed through Monto.
FAQs
Specific to using Monto API through Jentic.
Why is there no official OpenAPI spec for Monto API?
Monto does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Monto API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Monto API use?
Monto uses an API key in the Authorization header. Through Jentic the key is stored in the credential vault and applied to each request at execution time so it never enters the agent's context.
Which accounting systems does Monto unify?
Monto exposes a unified schema across underlying integrations such as QuickBooks Online and Xero through GET /integrations and the /companies/{company-uuid}/customer-invoices and account endpoints. The same field names and shapes apply regardless of the underlying ERP.
Can I pull a balance sheet through Monto?
Yes. The /balance-sheet endpoint returns a standardised balance sheet per company. The /income-statement endpoint provides the corresponding profit and loss view, and /metrics aggregates higher-level numbers across companies.
What are the rate limits for the Monto API?
The spec does not declare explicit rate limits. Treat HTTP 429 as a back-off signal and retry with exponential delay; long reports such as a 24-month income statement should be cached client-side.
How do I list every customer invoice for a company through Jentic?
Search Jentic for 'list customer invoices', load the schema for GET /companies/{company-uuid}/customer-invoices, and execute it with the company's UUID. Jentic handles the Authorization header so only the company UUID is needed.
Can I limit what my agent is allowed to do with the Monto API?
Yes. Because you run Jentic One yourself, your own rules decide which Monto operations and credentials the agent may use. Monto puts the company id in the URL path, such as /companies/{company-uuid}/customer-invoices, so you can pin the agent to a single company and let it read only that company's invoices, accounts, and financial statements. You choose which operations it may call, so a destructive one like DELETE /companies/{company-uuid} stays off unless you explicitly add it.
GET STARTED