API SuiteBusiness Verification (GST, Udyam, Udyog)
Upyog Details
Fetch legacy Udyog registration details. Server-side POST with Bearer auth; Udyog id in the path.
API reference
Try itLoading playground…
Loading…
AuthorizationBearer <token>
JWT Bearer token authentication. Obtain a token from the KwikID dashboard.
In: header
Path Parameters
udyog_idunknown
The udyog number for which data has to be fetched.
Default
""Format
stringResponse Body
curl -X POST "https://__mock__/verification/v2/udyog/get//"{
"message": "string"
}{
"detail": {
"<location>": {
"<field_name>": [
"string"
]
}
},
"message": "string"
}{
"detail": {},
"message": "string"
}Overview
Call POST /verification/v2/udyog/get/{udyog_id}/ from your backend with Authorization: Bearer <token> when the counterparty still references an older Udyog number. Replace {udyog_id} in the path. For new Udyam registrations, prefer Udyam Details.
Key features
- Legacy coverage: Handles portfolios that still store Udyog ids.
- Same auth model as other business verification routes.
Implementation
Step 1: Call from your backend
POST /verification/v2/udyog/get/<udyog_id>/ HTTP/1.1
Host: <verification-api-base-url>
Authorization: Bearer <token>
Content-Type: application/json
{}Error handling
| HTTP status | When |
|---|---|
| 400 | Validation error. |
| 401 | Invalid token. |
Benefits
- Lets you verify older MSME records without forcing users to migrate numbers immediately.