REST API · MCP
Invoice API and MCP Server
Connect an application or AI agent to the same governed invoice operations. Keys and OAuth grants carry explicit scopes, while every mutation carries a caller-owned idempotency key.
How it works
One command catalog, two transports
REST endpoints and MCP tools are derived from the same operation catalog, so a capability does not quietly exist on one transport and disappear on the other.
Grant only the scopes needed
Separate client, document, finalisation, tax and reporting scopes let a read-only integration stay read-only.
New API keys default to client and document reads.
Call a bounded operation
Find or create clients; list, read, draft, preview, finalise or download invoices; look up HSN/SAC; or read the aggregate report summary.
Every mutation requires an Idempotency-Key.
Receive the same result contract
The gateway applies authentication, scope, rate, allowance and idempotency checks before the shared command runs.
REST and MCP return the same narrowed operation result.
Controls and limits
Automation stops at the irreversible edges
The agent surface is useful without inheriting every action the signed-in product can perform.
- Delivery
- No API or MCP scope can send an invoice by email or WhatsApp.
- Payments
- No operation records, changes or collects a payment.
- IRN
- India e-invoice registration remains outside the agent surface.
- Secrets
- API keys are stored as SHA-256 digests; the plaintext is shown only when created.
Boundary
Finalisation is explicit
A credential can finalise only when it was granted the independent documents:finalize scope. Document write access does not imply it.
Get started
Create your first invoice.
Free from day one. Pro adds volume when your business asks for it.