Meesho Has No API: How to Automate Accounting Anyway

By TallySutra Team · 22 August 2026 · 5 min read

Search for "Meesho API integration" and you will find plenty of tools implying a live pipe into your supplier account. Here is the inconvenient fact underneath: Meesho has no documented public seller API. There is no sanctioned programmatic endpoint for third-party software to pull your orders, settlements or GST data. Understanding what that means, and what it does not mean, is the difference between automating your accounting safely and handing your panel credentials to something you should not trust.

What "no public API" actually implies

Any tool claiming live Meesho sync is doing one of three things: reading files a human exported (legitimate, just not "live"), asking for your panel login to scrape pages on your behalf (fragile, and a credential-safety question you should take seriously), or overstating its marketing. Scraping breaks whenever the panel changes, can misread data silently, and puts your account access inside someone else's infrastructure. When evaluating a vendor, ask one direct question: where exactly does my data enter your system? A trustworthy answer names the files.

The good news: the exports are excellent

Automation does not need an API; it needs structured, complete, authoritative data, and Meesho's panel exports provide exactly that:

• The GST sales report: sub-order-level rows with Sub Order No, Order Date, Event Type (Sale/Return/RTO), GST Rate, Taxable Value, IGST/CGST/SGST, Total Invoice Value and End Customer State.
• The payment statement: per sub order, Payment Date, UTR, Final Settlement Amount, Meesho Commission (incl. GST), GST on Commission, TCS and TDS.

These are the same documents your CA and any auditor would rely on, which is precisely why building books from them beats any unofficial pipe: the source of your vouchers is the official record itself, downloadable again by anyone who needs to verify.

File-based automation, end to end

Here is what the automated workflow looks like in practice with TallySutra's Meesho workflow, which is built deliberately and exclusively on file upload:

1. You export the two reports from the supplier panel, a two-minute human step that keeps you in control of what enters the pipeline.
2. You upload them to TallySutra. No panel credentials are ever requested; nothing is scraped.
3. The platform parses and validates every row: tax splits must sum, rates must be real slabs, Sub Order Nos must be new, recoveries must match booked sales.
4. Vouchers are generated: rate-wise sales, credit notes for Return and RTO events, commission split from its GST, TCS and TDS to receivables, UTR-grouped receipts, all balanced.
5. Exceptions queue for review and a CA approval step gates each batch.
6. Export to TallyPrime as standard Tally XML, or push via the Gateway desktop app (currently unsigned beta installers, so expect an OS publisher prompt).

"But manual export is a step backwards"

Accounting is a batch discipline. GST filings, settlements and bank statements all operate on periods, and the export-upload rhythm matches that reality perfectly. What actually matters is what happens after ingestion: validation, reconciliation by UTR, exception handling, duplicate safety, and CA oversight, the substance covered across our payout reconciliation guide and the rest of this series.

Questions to ask any Meesho tool vendor

• Do you request my supplier panel credentials? (The safe answer is no.)
• What exact files do you ingest, and do you accept them unmodified?
• What happens to rows that fail validation?
• If I upload the same period twice, what happens?
• Who approves vouchers before they reach Tally?

If Meesho ships a public seller API someday, file-based tools can adopt it; until then, claims of live sync deserve your skepticism, and official exports deserve your trust. Automation was never blocked by the missing API, only relocated to the step after download.

The bottom line for a supplier deciding today: the export-based path is not a compromise while you wait for something better, it is the accounting-grade design. Official files, human-controlled ingestion, validation before posting and an approval gate is the same architecture auditors have trusted for decades, applied to marketplace data. Choose tooling on the strength of that pipeline, not on connectivity claims nobody can verify.

Frequently asked questions

Related reading

• Meesho to Tally Import Errors and How to Fix Them
• Meesho TCS & TDS Compliance for Suppliers
• Meesho Supplier Bookkeeping: The Complete Guide