API

The Bizmitra REST API is HTTPS and JSON, versioned under /api/v1. It is the integration layer for TallyPrime: Tally itself exposes only a LAN-bound XML/TDL gateway, so this is the REST/JSON surface your application — or an MCP server for TallyPrime — actually calls.

https://bizmitra.io/api/v1

Quick orientation

GET https://bizmitra.io/api/v1/ping
Authorization: Bearer {key_id}:{secret}
Accept: application/json

Three things appear in almost every request:

Element	Value
Base URL	https://bizmitra.io
Auth header	Authorization: Bearer {key_id}:{secret}
Company	company_id query parameter, or the X-Bizmitra-Company header

Pages in this section

• Authentication — keys, headers, and rotation.
• Conventions — response envelopes, pagination, dates, identifiers.
• Errors — what failures mean and how to respond.
• API reference — the full endpoint surface.
• Versioning and lifecycle — compatibility guarantees and deprecation.

Endpoint families

Family	Purpose
Write	invoices, orders, credit-notes, debit-notes, purchases, receipts, payments, contras, journals
Read	pulled-vouchers, and its detail and acknowledgement endpoints
Transactions	Status of asynchronous work
Reports	stock-summary, stock/monthly, stock-tree, stock/vouchers, funds-flow, profit-loss, tds-summary, tds/bills
Masters	Create and track master jobs
Provisioning	applications, customers, companies
Connectors	Pairing codes, connector fleet, company health
Webhooks	Endpoints, secrets, test events, delivery history
Utility	ping, and the Tally bridge passthrough

Two things to internalize before you build

Writes are asynchronous. A success: true on a POST means accepted, not completed. Check the transaction. See Jobs and transactions.

Responses grow. New fields are added within v1. Ignore what you do not recognize rather than rejecting it, or a routine additive change will look like an outage on your side.