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

IEC Verification API

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.

Response
Real-time
Inputs
1 required · 1 optional
Consent
Not required
Billing
Per successful call
POST /v1/iec-verification
Sandbox · Production
  1. Your application sends

    • IEC number*
    • Company name
  2. emver API

    Validates the request, queries the source, normalises the answer and logs the call. Billed only on success.

  3. Verified with

    DGFT IEC registry

  4. You receive

    • Entity name
    • IEC status
    • Issue date
iec-verification Full reference
Overview

What the IEC Verification API does

Every business 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.

Benefits

Why teams use the IEC Verification API

Validate an Import Export Code and the entity behind it.

Source-verified

Straight from the foreign-trade registry.

Name check

Registered entity compared with the name you hold.

Real-time

Validate at shipper onboarding, not at customs.

Complete KYB

Combine with GSTIN, MCA and bank verification on the same key.

Use cases

Where it's called

Where the IEC Verification API is typically called, and what it settles there.

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.

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

    Send the inputs

    IEC number as a JSON body. Optional fields sharpen the match.

  3. 03

    We verify at source

    emver queries the authoritative record, normalises the answer and logs the request.

  4. 04

    Act on the result

    A verification status plus the fields listed above, in the same response envelope as every other API.

Privacy and security built in

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

FAQ

IEC Verification API: frequently asked questions

What teams ask before adding the IEC Verification API to their integration.

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.

The code has been suspended or cancelled. Shipments and finance against it should be held pending review.

Related

APIs that run alongside it

Usually called with the IEC Verification 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.