Udyam Verification API
Check an Udyam registration number and confirm the enterprise behind it. See how it is classified. Payment terms, procurement policy and credit decisions then rest on verified MSME status.
Overview
Udyam is the registration that records a business as a micro, small or medium enterprise in India. The classification it carries changes how a buyer has to pay, what a procurement team has to report, and how a lender may treat a file. Udyam verification checks a submitted registration number and returns the enterprise information available against it. Basic covers the identity and classification of the enterprise. Advanced adds the wider enterprise profile available for the registration. It suits teams that need activity, address and unit context before they approve a supplier. Available fields vary by data source and by the individual record, and the depth available depends on the service contract you select.
- Category
- KYB Services
- Coverage
- Udyam registrations issued to micro, small and medium enterprises in India
- Input
- A Udyam registration number
- Output
- The enterprise details and MSME classification available, with wider profile context at the Advanced depth
- Typical users
- Procurement, vendor onboarding, accounts payable, lending and merchant operations teams
- Coverage note
- Udyam registrations across India. Which fields you see depends on the data source and on the individual record.
The overview and the sections after the reference are the FinSour API catalog’s own record for this service, rendered unaltered.
Endpoint URL and method
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Authentication
Send your API key in this header on every call, from your own server: a key sent from a browser is refused. A key starting fs_test_ calls the sandbox and one starting fs_live_ calls production, at the same address. Create keys in the FinSour console.
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Request parameters
Headers
| Name | Type | Required | Description | Constraints |
|---|---|---|---|---|
Idempotency-Key | string | Required | A key you generate for each attempt. Sending the same key again returns the first answer instead of running the check twice; the same key with a different body is refused. | 8 to 255 characters. Matches ^[A-Za-z0-9._:-]+$ |
Body
| Name | Type | Required | Description | Constraints |
|---|---|---|---|---|
input | object | Required | The details to check. | — |
input. | string | Required | — | Matches ^UDYAM-[A-Z]{2}-[0-9]{2}-[0-9]{7}$ |
options | object | Optional | Settings for this call. | — |
options. | string | Optional | Your own reference for this call. It comes back unchanged as meta.reference. | 1 to 128 characters |
options. | object | Optional | The person's consent to this check. | — |
options. | boolean | Required | Send true once the person has agreed to the check. | Always true |
options. | string (date-time) | Required | When the person gave consent. | — |
options. | string | Required | What the check is for, for example kyc. | 1 to 64 characters |
Request samples
cURL
curl -X POST https://gateway.staging.finsour.io/v1/business/udyam \
-H "X-Api-Key: $FINSOUR_API_KEY" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{
"input": {
"udyamNumber": "<udyamNumber>"
}
}'Node.js
const response = await fetch("https://gateway.staging.finsour.io/v1/business/udyam", {
method: "POST",
headers: {
"X-Api-Key": process.env.FINSOUR_API_KEY,
"Idempotency-Key": crypto.randomUUID(),
"Content-Type": "application/json",
},
body: JSON.stringify({
"input": {
"udyamNumber": "<udyamNumber>"
}
}),
});
console.log(response.status, await response.json());Python
import os
import uuid
import requests
response = requests.post(
"https://gateway.staging.finsour.io/v1/business/udyam",
headers={
"X-Api-Key": os.environ["FINSOUR_API_KEY"],
"Idempotency-Key": str(uuid.uuid4()),
},
json={
"input": {
"udyamNumber": "<udyamNumber>",
},
},
timeout=30,
)
print(response.status_code, response.json())Generated from the fields above. Replace each value in angle brackets with your own; the key is read from FINSOUR_API_KEY.
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Response schema
| Name | Type | Present | Description | Constraints |
|---|---|---|---|---|
data | object | Always | The result of the check. | — |
data. | boolean | Always | — | — |
data. | string | Always | — | Matches ^UDYAM-[A-Z]{2}-[0-9]{2}-[0-9]{7}$ |
data. | object or any or null | Always | — | — |
data. | array of objects | Always | — | — |
data. | string or null | Always | — | — |
data. | object or any or null | Always | — | — |
data. | array of objects | Always | — | — |
data. | string or null | Always | The two-digit NIC code. | Matches ^[0-9]{2}$ |
data. | string or null | Always | The four-digit NIC code. | Matches ^[0-9]{4}$ |
data. | string or null | Always | The five-digit NIC code. | Matches ^[0-9]{5}$ |
data. | string or null | Always | The kind of activity (for example SERVICES), upper-cased, as given. | — |
data. | string or any or null | Always | The day the activity was added to the registration (Release 1.1). | — |
data. | string or null | Always | The activity's position in the registration's list, as given (Release 1.1). | — |
data. | object | Always | — | — |
data. | string | Always | When the answer was fetched: RFC 3339 UTC with a Z, never an epoch or an IST offset. | Matches ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(\.\d{1,9})?Z$ |
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Error codes
| Code | Status | Meaning | Retrying |
|---|---|---|---|
API_VERSION_UNSUPPORTED | 400 | That API version is no longer supported. | Do not retry automatically |
IDEMPOTENCY_KEY_INVALID | 400 | That Idempotency-Key does not meet the required format. | Do not retry automatically |
IDEMPOTENCY_KEY_REQUIRED | 400 | An Idempotency-Key header is required for this request. | Do not retry automatically |
REQUEST_MALFORMED | 400 | The request could not be parsed. | Do not retry automatically |
AUTH_KEY_EXPIRED | 401 | The API key is not valid. | Do not retry automatically |
AUTH_KEY_INVALID | 401 | The API key is not valid. | Do not retry automatically |
AUTH_KEY_MISSING | 401 | No API key was presented. | Do not retry automatically |
AUTH_KEY_REVOKED | 401 | The API key is not valid. | Do not retry automatically |
INSUFFICIENT_BALANCE | 402 | The available balance is not enough for this request. | Do not retry automatically |
AUTH_IP_NOT_ALLOWED | 403 | This API key may not be used from this address. | Do not retry automatically |
ENTITLEMENT_MISSING | 403 | This organization is not entitled to that product in this environment. | Do not retry automatically |
ORGANIZATION_SUSPENDED | 403 | This organization is not active. | Do not retry automatically |
PRODUCT_NOT_AVAILABLE | 403 | That product is not available. | Do not retry automatically |
PRODUCT_RETIRED | 403 | That product has been withdrawn. | Do not retry automatically |
SCOPE_INSUFFICIENT | 403 | This API key does not carry the scope this product requires. | Do not retry automatically |
PRODUCT_NOT_FOUND | 404 | No such product. | Do not retry automatically |
IDEMPOTENCY_KEY_REUSED | 409 | That idempotency key was already used for a different request. | Do not retry automatically |
PRICE_UNAVAILABLE | 409 | No active price covers this product right now. | Safe to retry |
REQUEST_IN_PROGRESS | 409 | An earlier attempt with this key is still running. | Safe to retry |
SETTLEMENT_PENDING | 409 | This request is awaiting reconciliation by an operator. | Do not retry automatically |
API_VERSION_SUNSET | 410 | That API version passed its announced sunset date. | Do not retry automatically |
REQUEST_TOO_LARGE | 413 | The request body is too large. | Do not retry automatically |
UNSUPPORTED_MEDIA_TYPE | 415 | That content type is not accepted on this route. | Do not retry automatically |
SANDBOX_FIXTURE_MISSING | 422 | No sandbox fixture exists for this input. Use a different test value. | Do not retry automatically |
UPSTREAM_REJECTED | 422 | The upstream source rejected the input. | Do not retry automatically |
VALIDATION_FAILED | 422 | The request payload is invalid. | Do not retry automatically |
CONCURRENCY_LIMIT | 429 | Too many simultaneous requests. | Safe to retry |
QUOTA_EXCEEDED | 429 | The allowance for this window is spent. | Do not retry automatically |
RATE_LIMITED | 429 | Too many requests. | Safe to retry |
INTERNAL_ERROR | 500 | An unexpected error occurred. | Safe to retry |
OUTCOME_UNCERTAIN | 502 | The outcome of this request is not yet known. Retry with the same Idempotency-Key. | Do not retry automatically |
UPSTREAM_UNAVAILABLE | 502 | The upstream source is unavailable. Retry shortly. | Safe to retry |
MAINTENANCE_MODE | 503 | The service is in a maintenance window. | Safe to retry |
NO_PROVIDER_AVAILABLE | 503 | No provider can serve this product right now. | Safe to retry |
SERVICE_OVERLOADED | 503 | The service is shedding load. Retry shortly. | Safe to retry |
UPSTREAM_TIMEOUT | 504 | The upstream source did not respond in time. | Safe to retry |
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Rate limits
| Scope | Limit | Window | At the limit |
|---|---|---|---|
| Your API key, within your organisation's limit | The figure in X-RateLimit-Limit | Per minute | 429 RATE_LIMITED, with Retry-After in seconds. Every answer past authentication carries X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset. |
Supplied by FinSour platform API contract (finsour development at 80e8b83bf) on . OpenAPI document at commit 436311c32, API version 2026-11-01. The beta is served from the staging gateway.
Use cases
- Procurement: confirm supplier MSME status before payment terms are agreed
- Lending and NBFC: confirm micro or small status before an MSME credit product applies
- Fintech and payments: classify a merchant at onboarding and apply the right limits
- Marketplaces: record verified seller MSME status in the vendor master at signup
- Logistics and fleet: check small transport and last-mile partners before onboarding
- Real estate: verify contractors and material suppliers before a site account opens
What this service does
What a Udyam response returns
The enterprise name and organization type, the micro, small or medium classification, and registration date and status context. Advanced adds activity, address and unit-level context. Which of those attributes you see depends on the data source and the individual registration.
Basic and Advanced on one page
Basic covers the identity and classification of the enterprise. Advanced adds the wider enterprise profile available for the registration, which suits supplier due diligence rather than a quick status check. The depth available depends on the service contract you select.
A status that drives payment terms
Settlement windows for micro and small suppliers, periodic reporting on outstanding dues, procurement set-asides and MSME credit products all depend on one thing. The status recorded in the supplier master has to be right.
Check at onboarding, re-check later
Classification can change as an enterprise grows. The same check supports a confirmation at onboarding and a periodic sweep across suppliers you have an active commercial relationship with.
How a check runs
Agree the depth you need
Tell us which checks you need and whether Basic or Advanced suits your workflow. Start with Get API, and we settle the service contract from there.
Connect the check to your supplier systems
Add the check to your supplier onboarding form, vendor master, procurement system, payables queue or review dashboard, following the documentation we provide at onboarding.
Send the Udyam number
Your application sends the Udyam registration number as the enterprise provided it, and we process the request at the agreed depth.
Read the enterprise details
The enterprise information and classification available come back in a structured response. Which fields are present depends on the data source and the individual registration.
Apply the classification
Use the classification to set payment terms, procurement treatment or credit eligibility. Store the response with its timestamp against the supplier record.
Questions
- What do I send to verify an Udyam registration?
- The Udyam registration number as the enterprise has provided it. No certificate upload or image is needed for this check.
- What is the difference between the Basic and Advanced depths?
- Basic confirms the registration and returns the enterprise identity with its micro, small or medium classification. Advanced adds the wider profile available for the registration, such as activity classification, address and unit-level context, and other identifiers recorded against it. This page covers both, and the depth available depends on the service contract you select.
- Why does MSME classification matter to a buyer?
- It changes the buyer's own obligations. Payments to micro and small suppliers carry a statutory settlement window that can affect how the expense is treated. Companies also report dues outstanding to those suppliers on a periodic return, and procurement policy sets aside a share of buying for them. Each of those depends on the status in the supplier master being correct.
- Can a supplier's MSME classification change?
- Yes. Classification follows the investment and turnover criteria that apply to the enterprise, so a growing supplier can move between categories and registration details can be updated. Most teams re-check suppliers they have an active commercial relationship with.
- What if the Udyam number is not found?
- Either the number could not be matched in the information available, or the enterprise is not registered. Registration is not universal, and a business may simply not hold one. An empty result is a normal outcome, and on its own it says nothing negative about a supplier.
- How do I get access to Udyam verification?
- Use Get API to tell us about your supplier workflow and volumes. We agree access, the supported depths and the integration documentation as part of the service contract.
Catalog entry last updated .