PIB TrackerFourteen agreements, three APIs, and an approval step that does not move
DGFT has opened three APIs so an exporter's own software can file for a certificate of origin and verify one. The approval step itself is unchanged.
What happened
- DGFT, under the Ministry of Commerce & Industry, introduced an Open API facility for the issuance and verification of Certificates of Origin on the Trade Connect e-Platform, under Trade Notice No. 25/2026-27 dated 7 September 2026.
- Until now exporters entered CoO details separately on the DGFT platform even when the same data already sat in their ERP or accounting software; the facility transfers it electronically instead.
- Three APIs are available — an Authentication Token API, a CoO File API for submitting applications and receiving certificates, and a Certificate Verification API — with credentials drawn from the API Management section of the CoO Portal against registered IP addresses.
- A transaction ledger carries each application through Draft, In Process, Approved, Certificate Issued and Rejected, and records the acknowledgement ID, file number, file date and certificate number.
- The framework spans fourteen named agreements, from India-Japan CEPA and the ASEAN-India FTA to India-EFTA TEPA and India-UK CETA, plus the Generalized System of Preferences and the Non-Preferential CoO Scheme.
For Prelims
- Certificate of Origin (CoO): the document evidencing where goods were made; DGFT opened an Open API for its issuance and verification on 7 September 2026.
- Preferential CoO: issued under FTAs, RTAs and PTAs, it is the document on which an exporter claims the applicable tariff concession in the importing country.
- Non-Preferential CoO: issued for customs clearance, compliance, trade remedy and other trade purposes, and carries no tariff benefit.
- Trade Connect e-Platform: the platform carrying the eCoO module; registration and integration are published at trade.gov.in, and the facility comes by Trade Notice No. 25/2026-27.
- The three APIs: Authentication Token for login, CoO File for submitting an application and receiving the certificate, and Certificate Verification for verifying one already issued.
- Origin criteria: the system automatically applies the fields, origin criteria and validation rules of whichever agreement or certification scheme the exporter selects.
- Security stack: SHA-256 RSA digital signatures on 2048-bit X.509 certificates, PBKDF2 password hashing with a dynamic salt, exporter-whitelisted IP addresses, and a 60-minute access token.
- Agreements covered: fourteen are named — CEPA/CECA with Japan, Korea, Singapore, Malaysia, UAE and Oman; SAFTA, SAPTA, ASEAN-India FTA; PTAs with Chile and Mercosur; Australia ECTA, EFTA TEPA, UK CETA — plus GSP.
For UPSC: Use it as the concrete instance of trade facilitation that is plumbing rather than policy: the state has changed how an application arrives, not what it must prove. It is also the cleanest hook for rules of origin, because the fourteen agreements named here are exactly where a preferential benefit is claimed or lost, and the preferential versus non-preferential distinction is worth a line of its own. It fits any question on why concluded trade agreements go under-utilised.
What it is NOT: The release gives no number of Certificates of Origin issued in a year, no count of designated issuing agencies, Export Promotion Councils or trade bodies on the system, and no processing time before or after — expedition is asserted, not measured. It also does not say that issuance becomes automatic: the ledger retains In Process, Approved and Rejected as distinct states, so the API changes the channel and not the decision, and the safeguards listed authenticate the sender cryptographically without any stated check on whether a claimed origin is true.
For Mains
Syllabus: GS3.8 · GS2.18 · Linkage L2
Anchor
Trade documents have been online for years; what changed on 7 September 2026 is that the exporter's own software now talks to the DGFT's. The reform is not a faster counter but the deletion of a re-typing step between two systems that already hold the same facts. Trade facilitation, at this stage, is an integration problem rather than a policy one.
Substantiation (data)
Three APIs — Authentication Token, CoO File and Certificate Verification; credentials issued through the CoO Portal's API Management section against exporter-whitelisted IP addresses; SHA-256 RSA signatures on 2048-bit X.509 certificates; a 60-minute access token; a ledger running Draft, In Process, Approved, Certificate Issued and Rejected; fourteen named agreements plus the Generalized System of Preferences.
Exemplification
Asked for a case where a trade agreement's benefit turns on paperwork, use the preferential Certificate of Origin. It is the document on which a concession under India-UAE CEPA, the ASEAN-India FTA or India-UK CETA is actually claimed, while the non-preferential certificate, issued for customs clearance and trade remedy, carries none. The system applies each agreement's own origin criteria automatically.
Problematisation
The gains are stated in process language — repetitive entry eliminated, errors reduced, the application expedited — while the release publishes no volume of certificates, no count of issuing agencies and no before-and-after processing time. A facility whose whole claim is speed reports no measurement of speed, so its effect cannot be assessed from this document.
Counterpoint
Against the reading that this automates issuance, the release never says so. Its safeguards establish that a message arrived unaltered from a registered exporter; they say nothing about whether the origin being claimed is true. The ledger keeps Approved and Rejected as separate outcomes, so a decision still sits between the application and the certificate.
Position
The defensible line is that machine-to-machine filing lowers the cost of claiming a preferential benefit without touching the substantive test for it. Where the framework names fourteen agreements and utilisation of each turns on rules-of-origin compliance, cheaper documentation is a real margin — but only so long as the certificate stays hard to obtain on a false claim.
Deploys into: Trade facilitation and ease of doing business · E-governance that changes a channel rather than a decision · Rules of origin and the under-utilisation of FTAs · India's external sector and export competitiveness · Digital public infrastructure in cross-border trade
Ministry of Commerce & Industry · 2026-09-07 · PRID 2307462 · PIB source ↗