DGFT Launches Open API Integration for Certificates of Origin on the Trade Connect e-Platform

The Directorate General of Foreign Trade (DGFT) has introduced Open API integration for Certificates of Origin (CoO) on its Trade Connect e-Platform (the common digital CoO platform, earlier known as the CoO portal). Announced through Trade Notice No. 25/2026-27 in early September 2026, the change lets exporters and their software providers submit CoO applications and receive issued-certificate data directly system-to-system, rather than logging in and typing each application by hand.

For exporters who file large volumes of preferential and non-preferential Certificates of Origin, this is a practical workflow change worth acting on now.

What Happened

DGFT has opened Application Programming Interfaces (APIs) on the Trade Connect e-Platform so that an exporter's own ERP, or a third-party service provider's software, can connect to the CoO system and exchange data automatically. In plain terms, the platform can now "talk to" business software: application details can be pushed in, and status and issued-certificate information can be pulled back, without manual re-entry on the portal.

The measure sits within DGFT's broader digitisation of the CoO framework, under which preferential CoOs (claimed under India's trade agreements) and non-preferential CoOs are applied for and issued electronically through the common platform. Open API is the next layer: automation of the data exchange itself.

Why This Matters

Certificates of Origin are among the most repetitive documents in export operations. A preferential CoO is what lets a buyer claim reduced or zero duty under an FTA such as India–UAE CEPA, India–Australia ECTA or the India–UK CETA; a non-preferential CoO simply certifies where goods were made. Exporters who ship regularly re-enter much the same consignor, consignee, invoice and product data again and again.

Machine-to-machine filing reduces that manual keying, cuts transcription errors, and speeds turnaround — especially valuable for high-frequency shippers and for aggregators or logistics providers filing on behalf of many clients.

Who's Affected

This affects exporters who apply for Certificates of Origin, the issuing agencies on the platform, and the ERP vendors, CHAs and service providers who file on exporters' behalf. Larger and more digitally mature exporters stand to gain most; small exporters filing the occasional certificate can continue using the portal directly.

Operational Detail

Open API integration is an option, not a replacement for the portal. Exporters can continue to file CoOs manually on the Trade Connect e-Platform. To use the API route, an exporter typically needs its ERP or a chosen service provider to build to DGFT's published API specifications and complete the platform's onboarding and authentication steps. Certificates continue to be issued by the designated agencies under the existing CoO rules; the API changes how data moves, not the underlying eligibility or documentary requirements.

What Exporters and Service Providers Should Do Now

• Check whether your export volume of preferential and non-preferential CoOs justifies API integration versus continuing on the portal.
• Ask your ERP vendor or CoO service provider whether they support, or plan to support, DGFT's Trade Connect Open API.
• Review the Trade Notice and the API documentation on the Trade Connect e-Platform for the technical specifications and onboarding steps.
• Confirm your digital signature, IEC and platform registrations are current before onboarding.
• Keep your product-to-FTA origin-criteria mapping accurate — automation speeds filing but does not check whether goods actually qualify for preference.

The Bigger Picture

The Open API launch continues a run of DGFT portal upgrades in 2026 aimed at ease of doing business, alongside automated Free Sale and Commerce Certificate issuance, enhancements to the PSIA/PSIC and Bank Guarantee modules, and API-based ICEGATE data flows for authorisation closure. The direction is consistent: less manual data entry, more system-to-system exchange. As India's FTA network widens, faster and more reliable CoO issuance directly supports exporters' ability to claim preferential access in destination markets.

Frequently Asked Questions

Is manual filing on the portal being withdrawn? No. API integration is an additional option. Exporters can keep filing CoOs directly on the Trade Connect e-Platform.

Does this change who issues the certificate? No. Certificates continue to be issued by the designated agencies under the existing CoO framework. Only the data-exchange mechanism is automated.

Do I need to build the API myself? Not necessarily. Many exporters will access it through their ERP vendor or a CoO service provider that integrates with DGFT's API.

Does using the API change origin eligibility? No. The origin criteria and documentary requirements under each trade agreement are unchanged. Ensure your goods genuinely meet the applicable rules of origin before claiming preference.

Conclusion

Open API integration for Certificates of Origin is a back-office efficiency upgrade with real value for high-volume exporters and service providers. It will not change what qualifies for a certificate, but it can materially cut the time and errors involved in getting one. Exporters should assess the fit for their volumes and coordinate early with their software providers.

This article is for general guidance only. Exporters should verify the current requirements and technical specifications on the DGFT Trade Connect e-Platform and the text of Trade Notice No. 25/2026-27 before acting.