IEC Verification

Business & KYB

Validate an Import Export Code and the entity behind it.

Confirm that an Import Export Code is registered with the Directorate General of Foreign Trade, that it is active, and that it belongs to the entity you are dealing with. Built for freight, customs, trade finance and cross-border marketplaces.

Endpoint

POST https://app.emver.io/api/sandbox/v1/iec-verification

Authorization: Bearer YOUR_API_KEY

Content-Type: application/json

Accept: application/json

Request parameters

Field	Type	Description
`i_e_c_number` required	string	IEC number
`company_name` optional	string	Company name

Example request

cURL

curl -X POST https://app.emver.io/api/sandbox/v1/iec-verification \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -d '{
    "i_e_c_number": "string",
    "company_name": "string"
}'

import requests

response = requests.post(
    "https://app.emver.io/api/sandbox/v1/iec-verification",
    headers={
        "Authorization": "Bearer YOUR_API_KEY",
        "Accept": "application/json",
    },
    json={
        "i_e_c_number": "string",
        "company_name": "string"
    },
    timeout=60,
)
response.raise_for_status()
data = response.json()

const response = await fetch("https://app.emver.io/api/sandbox/v1/iec-verification", {
  method: "POST",
  headers: {
    "Authorization": "Bearer YOUR_API_KEY",
    "Content-Type": "application/json",
    "Accept": "application/json",
  },
  body: JSON.stringify({
      "i_e_c_number": "string",
      "company_name": "string"
  }),
});

const data = await response.json();

$response = Http::withToken('YOUR_API_KEY')
    ->acceptJson()
    ->post('https://app.emver.io/api/sandbox/v1/iec-verification', {
        "i_e_c_number": "string",
        "company_name": "string"
    });

$data = $response->json();

Replace YOUR_API_KEY and the placeholder values. Use the switch above to see production URLs.

Response

Structure · 200

{
  "status": INTEGER,
  "message": STRING,
  "data": {
    "entity_name": STRING,
    "i_e_c_status": STRING,
    "issue_date": STRING
  }
}

Example · 200

{
  "status": 200,
  "message": "string",
  "data": {
    "entity_name": "string",
    "i_e_c_status": "string",
    "issue_date": "string"
  }
}

Error · 4xx / 5xx

{
  "status": INTEGER,
  "message": STRING
}

See Errors & status codes for what each status means and which calls are billed.

About this API

Every emver that imports or exports needs an IEC, and forwarders, banks and marketplaces routinely accept it on trust. The IEC Verification API checks the code at source and returns the entity name, status and issue date, so shipments and trade finance are only extended to genuinely registered traders.

Send the expected company name to have it compared with the registered entity, catching codes borrowed from other businesses.

Typical uses

Freight and logistics onboarding. Verify every shipper and consignee before accepting cargo.
Trade finance. Confirm exporter and importer registration for LC and bill discounting.
Cross-border marketplaces. Validate seller eligibility to export.
Customs brokerage compliance. Keep client IEC records verified and current.

Questions

Is IEC the same as GSTIN for exporters?: No. IEC is issued by the foreign-trade authority and is required for customs clearance. GSTIN is the tax registration. Verify both for a complete exporter profile.
What does an inactive status mean?: The code has been suspended or cancelled. Shipments and finance against it should be held pending review.