Build on the books, without touching the books
Your storefront, your delivery app, your reporting tool or your own bespoke system can read from and write to E-Khata Cloud through a versioned REST API, and hear about changes through signed webhooks. Tokens are scoped, writes are idempotent, every request is logged, and the specification is a file you can load into your tooling.
The E-Khata Cloud public API is a versioned REST surface at /public/v1, described by an OpenAPI specification you can download from the API itself. Access is by API token, created in Settings under Developers, with scopes that limit what each token can read or write and a rotate action that swaps a key without downtime. Writes require an Idempotency-Key, so a retried request cannot create a second invoice. Webhooks push product, party, order and invoice events to your endpoint with a signature, a delivery log and a replay button.
What the API and webhooks give you
Two directions, two mechanisms. The API is pull and write; webhooks are push.
Your system to E-Khata, through the API
- Create and update products, with prices and units
- Create and update parties (customers and suppliers)
- Create sales orders and invoices, posted into the books
- Read stock and inventory levels
- Read your own token's identity and scopes at /me
E-Khata to your system, through webhooks
- product.created, product.updated
- party.created, party.updated
- order.created, order.updated
- invoice.created, invoice.updated, invoice.cancelled
- webhook_endpoint.created, webhook_endpoint.deleted
How to get started with the E-Khata API
Everything a developer needs is in Settings, under Developers. No email to us is required to get a token.
- Create an API tokenSettings, then Developers. Name the token, pick its scopes, and copy the key. It is shown once and stored hashed.
- Load the OpenAPI specificationFetch /public/v1/openapi.json and import it into Postman, Insomnia or your code generator. A Postman collection is also published.
- Make a read callGET /public/v1/me returns the token's business and scopes. Then list products, parties or inventory.
- Make a write call with an Idempotency-KeyPOST a product, a party or an invoice with a unique Idempotency-Key header. Retry safely; the same key returns the same result.
- Register a webhook endpointAdd your HTTPS URL, choose the events, copy the signing secret, and press Test. Every delivery is logged and can be replayed.
Scoped tokens, rotated without downtime
A token is created with exactly the scopes it needs, read or write per resource, and nothing else. Rotate swaps the key while the old one keeps working for a grace period, so a deployment never goes dark. Tokens are shown once, stored hashed, and every request they make is logged with a summary you can read in Settings.
- Per-resource read and write scopes.
- Rotate in place; revoke at any time.
- Request log and summary per token.
Writes that cannot double-post
Networks retry. Without protection, a retried POST creates two invoices. The public API requires an Idempotency-Key on every write and returns the stored result for a repeated key, so your integration can retry freely. If posting to the books fails, the API returns an error rather than a success with missing accounting entries.
- Idempotency-Key required on writes, enforced by middleware.
- A failed accounting post returns 422, never a silent 201.
- Rate limits per token, with the limit visible in the response headers.
Webhooks with a signature, a log and a replay
Register an HTTPS endpoint, choose the events, and E-Khata signs each delivery with the endpoint's secret so you can verify it came from us. Deliveries are logged with the response your server gave, retried on failure, and any delivery can be replayed from the log while you are debugging. Rotate the secret whenever you like.
- Nine event types across products, parties, orders and invoices.
- Signed payloads, delivery history, retry, and one-click replay.
- Test button to send a sample event before you go live.
Documented, and used by our own connectors
The Shopify and WooCommerce integrations are built on the same surface, which is the strongest guarantee that it stays maintained. The OpenAPI file is generated from the code, so it does not drift from what the server does, and the envelopes for lists, errors and pagination are consistent across every resource.
- OpenAPI specification generated from the code.
- Consistent list, error and pagination envelopes.
- A published Postman collection.
Who it is for
Frequently asked questions
Explore more of E-Khata
دیکھیں کہ آپ کا کاروبار ای کھاتا پر کیسے چلتا ہے۔
30 منٹ کی زوم یا واٹس ایپ کال۔ ہم آپ کو ای کھاتا دکھائیں گے۔
“میں یا میرا کو-فاؤنڈر ہر ڈیمو کال میں خود شامل ہوتا ہوں۔”
یا واٹس ایپ پر پیغام بھیجیں: +92 300 1676722 (1 گھنٹے میں جواب)۔