Skip to main content

// a DL Minds product

GSTIN API — GST Verification as a REST Endpoint

We built and run GSTIN API, a verification service for Indian GST identification numbers. One authenticated call returns the taxpayer's legal name, registration status, principal address, recent GSTR filing history and e-invoicing status — the checks a finance or procurement team would otherwise do by hand on the GST portal.

Signing up gives you 20 free verification credits after email confirmation. There is also a free GST number search tool if you only need to look up one number.

Why We Built It

GST verification kept turning up as the same small, annoying problem across client projects. An ERP rollout needs to validate a vendor master. A billing system needs to confirm a customer's GSTIN is still active before it raises a tax invoice. A marketplace needs to check sellers at onboarding. Every one of those teams ends up writing the same brittle thing: a regex that checks the 15-character shape, and a human who opens the GST portal when it matters.

A regex is not verification. It confirms the string is well formed; it tells you nothing about whether the registration exists, whether it is still active, whose name is on it, or whether the vendor has filed a return in the last year. That last question is the expensive one — input tax credit depends on your supplier actually filing, and by the time a mismatch surfaces in reconciliation the money has already moved.

So we built the check once, properly, and made it an API. It is the same thing we do inside CRM and ERP builds for clients, pulled out into a product any team can call.

What a Verification Returns

A single GET /api/get-taxpayer-info/{gstin} against the documented endpoint, authenticated with an x-api-key header, returns JSON covering four things:

Identity

The legal business name on the registration, so you can match it against what the vendor told you rather than trusting the form.

Registration status

Whether the GSTIN is currently active, plus the original registration date and the principal place of business.

Filing history

Recent GSTR filing records. This is the field that predicts input tax credit problems, and the one a format check can never give you.

E-invoicing and e-way bill status

Whether the taxpayer is in scope for e-invoicing and their e-way bill activity — relevant before you decide how to issue documents to them.

Bulk Verification for Vendor Masters

Onboarding checks are one call at a time. Cleaning an existing vendor master is not — it is usually a spreadsheet with a few thousand rows that nobody has verified since it was imported. For that, GSTIN API takes a job of up to 10,000 GSTINs, processes it asynchronously, and lets you poll for status and pull results back as JSON or CSV.

That shape matters more than it sounds. Firing ten thousand synchronous requests at any government-backed data source is how you get rate limited; submitting one job and collecting the results is how you finish the run.

The bulk endpoints are documented here →

Pricing

Usage-based, no subscription. You buy credits and spend one per successful verification. Invalid formats, numbers that do not exist and upstream errors are not charged — you only pay when you get real data back.

Tier Price per verification
Free credits on signup 20 credits, after email verification
Standard (under 2,500 credits) ₹0.50
Bulk (2,500 credits and above) ₹0.40

Current rates are published on the GSTIN API pricing page; that page is the source of truth if the two ever disagree.

Who Builds and Runs It

GSTIN API is owned and operated by DL Minds — the same team behind our web development, AI and CRM/ERP client work. Support and billing questions for the product go through gstinapi.com; if you want the verification logic embedded in a system we build for you instead, talk to us here.

Try it with 20 free credits

Create an account, confirm your email, and you have enough credits to verify twenty GSTINs before you decide whether it belongs in your stack.