How do I authenticate?

A Bearer token of the form KEY_ID:SECRET, plus an X-Bizmitra-Company header on company-scoped calls.

Is there a Postman collection?

Yes — the portal generates a Postman v2.1 collection of every endpoint you can access.

Tally REST API — JSON Endpoints for Tally

A Tally REST API means you work the way you already do: HTTP verbs, JSON bodies, status codes and a Postman collection. Bizmitra Connect provides exactly that — and translates to Tally’s native XML behind the scenes, on the customer’s machine.

Authentication

Every request carries an Authorization: Bearer KEY_ID:SECRET header. Data-plane calls that target a specific customer also send an X-Bizmitra-Company header. Sandbox and production keys are separate, so you can test safely.

Endpoints

The surface is grouped by purpose: transaction endpoints (sync invoice, sync sales order, pull vouchers), master endpoints (push ledgers, stock items and other masters), and control-plane endpoints (applications, companies, connectors, pairing codes). All are under /v1.

# POST /v1/invoices — create a voucher in Tallycurl -X POST https://api.bizmitra.io/v1/invoices \ -H "Authorization: Bearer KEY_ID:SECRET" \ -H "X-Bizmitra-Company: 345" \ -d '{ "event_type": "invoice_create", "invoice": { … } }'

Errors & status

You get standard HTTP status codes and JSON error bodies. A push that needs a paired, online connector returns a clear connector_timeout rather than failing silently, so your retries are easy to reason about.

Try it without writing code

Import the ready-made Postman collection, point it at the sandbox, and run a real request in minutes. The portal’s API Explorer lets you fire safe calls straight from the browser.

What you get

Bearer-token authentication Versioned /v1 endpoints Plain JSON request & response Sandbox + production keys Postman collection In-browser API Explorer

Documentation