Skip to main content
FinocketFinocket
Get Started

Public API & webhooks

AI that actually reads your books

A versioned REST API over 92 resources, signed outbound webhooks, and 256 MCP tools so Claude, ChatGPT or your own agents can work your books safely.

Start freeAll modules

What it solves

Your books are the source of truth about your business, but most software keeps them locked behind an app you have to click through. Open them over a real, versioned API and signed webhooks, and over MCP, so an AI agent can answer 'who owes me the most?' or 'what's my GST this month?' from your actual data instead of a guess.

How we're different

Everything you can do in the app you can do over the API, and everything the API can read, an AI agent can read through the MCP endpoint. The same read layer, scope-enforced, powers all three. Private and ledger data is never exposed over the API, and every row is scoped by row-level security.

The developer surface in Finocket: API keys, products, webhooks, request logs and the API reference
Finocket dashboard showing earnings, spend and outstanding at a glance
What it does

Inside Public API & webhooks

01

Public REST API v1 — 92 resources

Clients, leads, contacts, invoices, payments, payment links, payment allocations, deals, pipelines, tasks, tags, activities, calls, visits, consent, partners, partner applications, commission events, commission statements, referral links, attributions, a partner reading its own account, merchants, subscriptions, usage, companies, employees, onboarding, expenses, items, stock, stock transfers, stock counts, point of sale, stores, reports, GST returns, journals, ledger accounts, sales orders, purchase orders, goods receipts, RFQs, QR codes, custom fields, approvals, workflows, fixed assets, deferrals, banking (credit-card accounts), work centers, catalog, vendor portal tokens, report schedules, rate cards, records, record files, WhatsApp templates, template variants, campaign segments, email engagement, website chat, mailbox triage, mail intake, connected credentials, research facts, automation suggestions, Tally sync runs, scheduled agents, agent templates, loyalty and gift vouchers, promotions, shipments, compliance obligations, imports, jewellery, pharmacy, stays, restaurant, retail counter, manufacturing, textile, contractors, agri mandi, pharma distribution, FMCG distribution, professional practices, online carts and checkouts, marketplace settlements with claims & TCS/TDS registers, and support cases — versioned, key-scoped and multi-company aware, with an OpenAPI spec and a Scalar reference.
The developer surface in Finocket: API keys, products, webhooks, request logs and the API reference
02

AI over your books (MCP) - 256 tools

An MCP server exposes 256 scope-enforced tools across books, GST, inventory, CRM, point of sale, assets, partners and reports, so AI agents can read receivables, a GST return, a client statement, a consolidated group report, a working-capital view or a Tally export, and write through the same posters the app uses, inside the company you point them at.
Finocket dashboard showing earnings, spend and outstanding at a glance
03

The tools it deliberately withholds

Some capabilities are kept off the tool surface on purpose, each for a stated reason: approving a growth campaign (it would let one model approve another model's outreach), changing the AI autonomy dial (an agent could widen its own blast radius), approving a GST-notice reply (it exists to evidence that a named human read it), and the personal-tax screens (there is no tax scope, and hanging them off a reports scope would silently widen every existing third-party key to the owner's own income).

Public API & webhooks

The tools it deliberately withholds

04

The spec is checked against the code

The OpenAPI document is guard-tested against the filesystem in both directions (verbs declared versus verbs actually present, and declared scopes versus the scopes the routes enforce), so the reference can't quietly drift from the API. Before you integrate, note that `amount` fields are decimal major units, while any `_minor` field is integer paise.

Public API & webhooks

The spec is checked against the code

05

Signed outbound webhooks

A per-tenant webhook outbox with signed delivery fires on new company, expense, item or credit note, and a stock.low alert the moment a tracked item hits reorder level, so your own systems stay in sync in real time.

Public API & webhooks

Signed outbound webhooks

More in Public API & webhooks

Secure by construction

Every row is scoped by Postgres row-level security, private and ledger data is never exposed over the API, and credentials are AES-256-GCM encrypted.

Works with the rest of Finocket

AI assistant
The same read layer powers the REST API, the MCP tools and the in-app AI assistant.
Invoices & payments
Create and send invoices programmatically over REST, exactly as you would in the app.
Developers & API
The developer console issues and scopes the keys this API and its webhooks use.

Part of Developer & AI. See how every module connects.

Questions

Can an AI assistant really read my books?

Yes. An MCP server exposes 256 scope-enforced tools over your invoices, payments, CRM, expenses, stock, assets, partners and financial reports, so you can point Claude, ChatGPT or your own agent at a company and get real answers from your data. Private and ledger data stays off-limits, and every read is scoped by row-level security.

Is there anything an AI agent deliberately can't do?

Yes, and the reasons are recorded. It cannot approve a growth campaign (that would let one model approve another model's outreach), change the AI autonomy dial (an agent could widen its own blast radius), approve a GST-notice reply (that step exists to evidence a named human read it), or reach the personal-tax screens (there is no tax scope, and attaching them to a reports scope would silently widen every existing third-party key to the owner's own income).

Is the API stable enough to build on?

It's a versioned REST v1 with an OpenAPI spec, a Scalar reference and OAuth clients, covering 92 resources, and the spec is guard-tested against the filesystem in both directions, so it can't drift from the code. It is the same data layer the app itself runs on. The v1 API is the contract, and a breaking change would mean v2, not a silent edit.

You connect Finocket to the rest of your systems on a contract that does not break under you.

Where this wins

Public REST API + MCP (AI reads your books)Marg ERP does not have this

Ready to ditch the spreadsheet?

Free for solo users until 31 Dec 2026 — no partner code needed. ₹99/month after that. No credit card. Your books stay yours.

Start freeLog in