DGFT Opens Certificate-of-Origin APIs, Letting Exporters File Directly From ERP Systems

# DGFT Opens Certificate-of-Origin APIs, Letting Exporters File Directly From ERP Systems

Finin2min 2-minute summary

DGFT launched Open APIs for issuance and verification of Certificates of Origin through Trade Connect, covering both preferential and non-preferential CoOs and enabling eligible exporters to connect ERP or accounting systems directly.

**What changed:** Eligible exporters can now integrate their own ERP/accounting software with DGFT’s CoO system instead of re-entering the same application data manually.

**Why it matters:** The change can reduce repetitive data entry and errors while making origin-document workflows more scalable for exporters using multiple trade agreements.

**Who is affected:** Exporters, customs and trade-compliance teams, ERP providers, Export Promotion Councils, CoO issuing agencies and advisers handling FTA origin documentation.

**Action required:** Exporters should map CoO data fields to ERP masters, obtain API credentials, whitelist authorised IPs, test digital-signature controls and keep origin-supporting records separate from the transmission layer.

Release and dedupe status

This item passed semantic-deduplication against the latest 5–6 September FinNews baseline and is treated as a **new canonical**.

**Research cut-off:** 2026-09-07 20:00 IST

Key verified facts

• The Open API covers issuance and verification of Certificates of Origin through Trade Connect.
• It supports preferential and non-preferential CoOs.
• Three APIs are available: Authentication Token, CoO File, and Certificate Verification.
• Requests and responses use SHA-256 RSA digital signatures with 2048-bit X.509 certificates.
• Passwords use PBKDF2 with dynamic salt; access is IP-whitelisted; access tokens remain valid for 60 minutes.
• DGFT cites Trade Notice No. 25/2026-27 dated 7 September 2026.

Finin2min analysis

• This is a workflow digitisation change, not a relaxation of rules of origin. Exporters still need documentary evidence that goods satisfy the selected agreement’s origin criteria.
• API integration can materially lower manual-keying risk for high-volume exporters, but it also shifts control importance toward master-data governance, authentication and change management.
• Preferential CoO errors can trigger denied tariff preference or post-clearance disputes overseas, so automation should preserve maker-checker controls.
• The certificate-verification API can improve downstream validation for counterparties and compliance teams.

Finance, tax, legal and control lens

The reporting above separates confirmed source facts from Finin2min interpretation. A market report is not treated as a regulator filing, and a source-based estimate is explicitly attributed. Where a number is calculated from multiple official releases, the calculation is labelled rather than presented as an official published aggregate.

For finance teams, the practical test is whether this development changes cash flow, funding cost, liquidity, FX or commodity exposure, valuation assumptions, provisioning, covenant headroom or capital allocation. For regulated or legal developments, the operative instrument controls; a headline or similarly titled historical circular is not substituted for the current document.

Tax treatment can depend on the instrument, transaction route, holding facts and effective law. Nothing in this article should be read as a personalised tax position. Businesses should preserve the controlling release, filing or circular and document the date on which it was relied upon.

What to watch next

• DGFT technical manual and API uptime
• Exporter ERP integrations
• Agreement-specific validation behaviour
• Customs acceptance and exception handling
• Cybersecurity/change-control incidents

Frequently asked questions

Does the API change FTA origin rules?

No. It changes the application and verification interface. Origin criteria continue to depend on the relevant FTA/PTA/CEPA/CECA or non-preferential scheme.

Which CoOs are covered?

DGFT says both preferential and non-preferential Certificates of Origin are supported.

What are the main security controls?

DGFT specifies digitally signed requests/responses, PBKDF2 password protection, IP whitelisting and time-limited access tokens.

Source and methodology

- Controlling source: DGFT / Ministry of Commerce & Industry / PIB — https://www.pib.gov.in/PressReleasePage.aspx?PRID=2307462

Finin2min used a primary-source-first hierarchy. Reuters is used as the controlling wire source for live market, FX and global developments where it is the best available verified real-time source. Competitor finance portals are not used as controlling sources in this release batch. The story was checked against the latest available FinNews package and CMS activity baseline to reduce semantic duplication.

Disclaimer

This material is for information and education only. It is not investment, tax, legal or financial advice. Market prices can move after the stated research cut-off. Verify the latest controlling source and obtain appropriate professional advice before acting on a material decision.