One call instead of three: the GSTIN Complete Profile endpoint

A useful vendor check needs three facts that live behind three separate calls: the registration record, the filing history, and whether the vendor files monthly or quarterly. Doing them separately means three requests, three credits and three places to handle an error. The complete-profile endpoint runs the same logic as the Excel output of our bulk GSTIN check and returns the distilled answer in one response.

This is the response for 33AAACC1206D1ZN, the public-sector GSTIN used in our documentation, from a call made on 4 October 2026. The billing fields that follow the profile are left out here.

GET /v1/gstin/33AAACC1206D1ZN/complete
x-api-key: YOUR_KEY

{
  "success": true,
  "gstin": "33AAACC1206D1ZN",
  "profile": {
    "legal_name": "CENTRAL WAREHOUSING CORPORATION",
    "trade_name": "CENTRAL WAREHOUSING CORPORATION",
    "registration_date": "2017-07-01",
    "business_constitution": "Created under special act of parliament",
    "status": "Active",
    "taxpayer_type": "Regular",
    "address": "No.4, Thiruvalar Illam, North Avenue, Srinagar Colony, Saidapet, Chennai",
    "filing_frequency": "Monthly",
    "gstr3b_filed_till": "2026-08",
    "gstr1_filed_till": "2026-08"
  }
}

• legal_name, trade_name, registration_date, status, taxpayer_type and address come from the registration lookup, the same record the plain verify call returns.
• business_constitution is the constitution of business from that record, with a fallback source where it is missing. It can be null.
• filing_frequency is "Monthly" or "Quarterly" for the latest quarter, from the filing preference. It can be null.
• gstr3b_filed_till and gstr1_filed_till are the latest filed period, as YYYY-MM, across the current and the previous financial year. They can be null.

These last four are best-effort. If the registration lookup succeeds but a supplementary source fails, that field is null rather than the whole call failing, the response sets partial to true, and the field is named in an unavailable array, for example ["filing_frequency"]. A null that is not named there means the source answered and had nothing, such as a GSTIN that has not yet filed a GSTR-1. So a listed null means "unknown", not "none": it does not mean the vendor files neither monthly nor quarterly, or that nothing was ever filed. A call that returns the registration is billed as one 2-credit call whether or not partial is set, and a retry is a new call that is billed again.

Not included: e-invoicing status, jurisdiction and additional places of business (the plain verify call returns those with the profile option), and the per-return-type compliance summary with filing lag (use the compliance endpoint).

The endpoint costs 2 credits. At default pricing the three separate calls it replaces (verify, returns and filing preference) cost 3 credits, so it is cheaper by a third, and one request instead of three. The credit price of each capability is configurable in our pricing table, so check your dashboard if you have a custom arrangement.

Failures are not billed. An invalid GSTIN returns 400 with a hint for fixing it, and the documented test GSTIN 00AAAAA0000A1ZT is free. A GSTIN not found in the GST database returns 404. A provider failure returns 502, and the right response is to retry with backoff (2, 4, then 8 seconds). The endpoint shares the API's rate limit of 60 requests per 60 seconds.

Use it for onboarding and due-diligence checks where you want a single snapshot of a vendor: is it active, what is it, does it file regularly and until when. Use the separate endpoints when you need the full return list with ARNs, the per-quarter filing preference, or the compliance summary. Whichever you use, the data is a live lookup, so the answer is true on the day you ask; store it with its date.