Free demo hits. Pay when you go live. Request access
Business & KYB

GST Verification with OTP API

With the taxpayer's OTP consent, fetch the full GST profile — registration details, principal and additional places of business, filing frequency and return history — for a deeper KYB than the public lookup allows.

Response
Async, by webhook
Inputs
1 required · 1 optional
Consent
Recorded per request
Billing
Per successful call
POST /v1/gst-otp-verification
Sandbox · Production
  1. Your application sends

    • GSTIN*
    • OTP (second step)
  2. emver API

    Issues a hosted consent link, tracks the person's authorisation and assembles the result.

  3. Completed via

    Authoritative source

  4. You receive by webhook

    • Legal name
    • Trade name
    • Places of business
    • Filing frequency
    • Return filing history
    • Turnover band
gst-otp-verification Full reference
Overview

What the GST Verification with OTP API does

Start the flow with the GSTIN; an OTP goes to the mobile registered with GST. Once the taxpayer confirms it, the API returns the detailed profile and up to the last 24 months of return filings, the basis for turnover-linked credit decisions.

Consent is part of the contract

The taxpayer authorises the pull by entering the OTP sent to their GST-registered mobile.

Benefits

Why teams use the GST Verification with OTP API

Consented GST pull: OTP to the registered mobile, then the complete profile and filing history.

Turnover you can lend on

Filing history and turnover bands straight from the network.

Consent built in

The OTP is the consent record.

Use cases

Where it's called

Where the GST Verification with OTP API is typically called, and what it settles there.

MSME lending

Underwrite on filed returns instead of self-declared turnover.

Supplier onboarding

Confirm compliance before large contracts.

How it works

Four steps, one response envelope

Request and response details, environments and a ready-to-import collection are in the developer console.

  1. 01

    Authenticate

    Call with your organisation API key. Sandbox and production use the same contract.

  2. 02

    Create the consent link

    Send the person's details and the documents you need. You receive a hosted link to share on any channel.

  3. 03

    The person authorises

    They sign in and choose what to share. Nothing moves without their approval.

  4. 04

    Receive the result

    Verified documents and details arrive by webhook or on the status endpoint.

Privacy and security built in

Consent recorded · Payloads not retained beyond your retention window · Every request traceable

FAQ

GST Verification with OTP API: frequently asked questions

What teams ask before adding the GST Verification with OTP API to their integration.

GSTIN Verification uses public data and needs no consent. This flow needs the taxpayer's OTP and returns the detailed profile and filing history.

Related

APIs that run alongside it

Usually called with the GST Verification with OTP API, on the same key.

All APIs
Access usually set up within one working day

Start verifying with emver today.

Tell us which APIs and what monthly volume. We set up your organisation, approve the APIs with demo hits and share per-call pricing.