GST API access
There are two ways to reach GST data programmatically. Filing, e-invoicing and e-way bill APIs run through a GSTN-licensed GST Suvidha Provider and need the taxpayer’s own authorisation. Verifying somebody else’s GSTIN needs neither — that data is public, and access is an API key away. This page is about which route you actually need, and what each one costs in time.
Three routes to GST data, and who each one is for
GSTN does not hand out a single "GST API". It licenses intermediaries, and the access model differs sharply depending on whether you are acting for a taxpayer or looking at one.
Become a GSP yourself
GSTN licenses GST Suvidha Providers directly. Selection rounds carry eligibility criteria around financial standing and IT capability, a security audit, a signed agreement with GSTN and licence fees. You then build and operate the integration yourself.
- Who:
- Large software vendors, banks, ERP companies
- Time to first call:
- Months — application windows are periodic
Build on a GSP as an ASP
Application Service Providers contract with a licensed GSP and consume its APIs. This is the normal route if your product genuinely files returns or generates IRNs on a taxpayer’s behalf, because those calls need the taxpayer’s own authorisation.
- Who:
- Products that need filing, e-invoicing or e-way bill APIs
- Time to first call:
- Weeks — commercial agreement plus integration
Use an aggregator verification API
For public taxpayer data, no licence and no taxpayer consent is involved. You sign up, take an API key and call a REST endpoint. That is what this API is: GSTIN verification and taxpayer data, not filing.
- Who:
- Anyone verifying counterparties — vendors, customers, sellers
- Time to first call:
- Minutes — sign up and call
If you are unsure which you need, the test is simple: does your feature write anything into GST records? If yes, you need a GSP. If it only reads who a GSTIN belongs to and whether it is live, you do not. See what a GST API does for the wider picture.
What access actually requires
Getting an API key here
1. Create an account
Sign up with an email address. No sales call, no KYC pack, no company registration documents to upload before you can test.
2. Verify your email
Verification releases 20 free credits automatically. They expire 30 days after issue, so use them while you are actually building.
3. Generate an API key
Create a key in the dashboard. It goes in the x-api-key header on every request. Keys can be rotated or revoked at any time.
4. Make the first call
One GET request against a real GSTIN. There is no approval queue between key generation and your first live response.
One request, one response
A single REST endpoint, authenticated with one header. This is the whole surface area — there is no OAuth dance, no session token to refresh, and no SDK you are obliged to install.
curl -s https://gstinapi.com/api/get-taxpayer-info/27AAACR5055K1Z7 \
-H "x-api-key: YOUR_API_KEY"
The response is JSON, shaped like this (abridged):
{
"taxpayer_data": {
"gstin": "27AAACR5055K1Z7",
"name": "RELIANCE INDUSTRIES LIMITED",
"tradename": "RELIANCE INDUSTRIES LIMITED",
"status": "Active",
"registrationDate": "01/07/2017",
"constitution": "Public Limited Company",
"einvoiceStatus": "Yes",
"pradr": {
"addr": { "bno": "...", "st": "...", "loc": "...", "stcd": "Maharashtra", "pncd": "400002" }
}
},
"filing_data": [
{ "rtntype": "GSTR3B", "taxp": "Jul", "fy": "2026-27", "arn": "AA27...", "dof": "18/08/2026" }
],
"nc_data": { "ewbstatus": "..." }
}
Full field-by-field reference is in the API docs, with runnable snippets for JavaScript, PHP and Python on the developers page.
What this access does and does not give you
Being straight about scope saves you a wasted integration week. This is a verification and taxpayer-data API. It is not a filing platform.
Included
- Legal name and trade name of the registered taxpayer
- Registration status — Active, Cancelled or Suspended
- Date of registration, constitution of business and taxpayer type
- Principal place of business address as a structured object
- Recent GSTR filing history with period, ARN and filed status
- e-invoicing enablement and recent e-way bill activity
Not included — needs a GSP
- Filing GSTR-1, GSTR-3B or any other return on a taxpayer’s behalf
- Generating IRNs or e-invoices — that runs through the IRP with its own credentials
- Generating or cancelling e-way bills
- Pulling GSTR-2A/2B or ledger data for a taxpayer you do not represent
- Anything requiring a taxpayer’s username and OTP-based API authorisation
Limits, credits and failure modes
| Concern | Position |
|---|---|
| Environments | One base URL. Free signup credits are the trial; there is no drifting mock sandbox. |
| Rate limiting | Per API key. Handle 429 with backoff and jitter, not an immediate retry. Ask if you need a higher ceiling. |
| Cost per call | One credit per successful lookup — ₹0.50, or ₹0.40 at 2,500+ credits. See pricing. |
| Free credits | 20 on email verification, expiring 30 days after issue. |
| 401 / 402 | Missing or invalid API key / zero credit balance. Both return JSON, not HTML. |
| 502 | Upstream government source unreachable or erroring. No credit is deducted. |
| Invalid GSTIN | Rejected on format and check digit before any upstream call, and never billed. |
Deeper reading: rate limits, retries and webhooks, the GST API error code guide, and why scraping the GST portal is the wrong kind of access.
GST API access — common questions
Get access and make a real call today
Twenty free credits, a live endpoint, and no approval queue between you and the first response.