DGFT Introduces Open API for Certificate of Origin: What Exporters Need to Know in 2026
Quick note
Below is the official summary and the reference document preview. Use โOpen PDFโ for full screen view.
Schedule a Call Back
300+ import-export and DGFT assignments since 2018
Clients include Advantech Industrial Computing India, Smiths Detection Systems, Areca Embedded Systems, Motorola Solutions India, Trinity Mobile APP Lab, Motorica India, Glocal Healthcare Systems, Tablets (India)Limited, Auroras TEA Company, Surabhi Aqua Minerals, Solankili Logistics Management, ATG Freight India (12 of 250+ served since 2018).
A few more clients we've served in this industryHide the list
- Electronics and technology
- Advantech Industrial Computing India ยท Smiths Detection Systems ยท Areca Embedded Systems ยท Motorola Solutions India ยท Trinity Mobile APP Lab
- Pharma and healthcare
- Motorica India ยท Glocal Healthcare Systems ยท Tablets (India)Limited
- Food and consumer goods
- Auroras TEA Company ยท Surabhi Aqua Minerals
- Logistics and trade
- Solankili Logistics Management ยท ATG Freight India
- Jewellery
- Janki Jewellers ยท Viindhya Bullion
- More clients
- Esskay Compuservices ยท Welgrow Technologies ยท Ample Technologies ยท Aprodite Infotech ยท Floroma Infinity ยท Moonlight Technology ยท NJ Power ยท Ample Digital ยท Augustdevices India ยท Automap Software and Technologies ยท SNS Metpro Industries ยท Webmeditech Healthcare ยท Anagh Traders ยท Meritech India ยท Zipped Solutions ยท Metanovo Health ยท Kapemai Lifestyle ยท Zexcorp Services ยท Agricapita Innotech ยท Meticulous Networks ยท Nexavarge ยท Arng ยท D13 Business Ventures ยท Datalux Systems India
Summary
The Directorate General of Foreign Trade (DGFT), under the Ministry of Commerce and Industry, has introduced an Open Application Programming Interface (API) facility for Certificates of Origin (CoO) through the Trade Connect e-Platform. The announcement was issued on 7 September 2026 and refers exporters to Trade Notice No. 25/2026-27 dated 7 September 2026 for further details.
The facility allows eligible exporters to connect their Enterprise Resource Planning (ERP), accounting, or other business software directly with DGFT's CoO system. Instead of entering the same information separately on the portal when it already exists in business software, application data can be transferred electronically. DGFT says this can reduce repetitive data entry, lower data-entry errors, and speed up the application process.
The facility covers both Preferential and Non-Preferential Certificates of Origin and provides separate APIs for authentication, application exchange, and certificate verification.
DGFT Open API for Certificate of Origin Notification at a Glance
| Particular | Verified Details |
| Ministry | Ministry of Commerce and Industry |
| Authority | Directorate General of Foreign Trade |
| Announcement | Open API Facility for Certificate of Origin |
| Announcement date | 7 September 2026 |
| Relevant Trade Notice | Trade Notice No. 25/2026-27 |
| Trade Notice date | 7 September 2026 |
| Platform | Trade Connect e-Platform |
| Facility | Open Application Programming Interface for CoO issuance and verification |
| Certificates covered | Preferential and Non-Preferential CoO |
| Users mentioned | Eligible exporters and their systems |
| Software integration | ERP, accounting, and other business software |
| APIs available | Authentication Token API, CoO File API, Certificate Verification API |
| Application tracking | Transaction ledger |
| Access-token validity | 60 minutes |
| Mandatory adoption deadline | Not expressly specified in the PIB release |
| Separate API fee | Not expressly specified in the PIB release |
The announcement is primarily a digital filing and system-integration development. It should not be read as a new Certificate of Origin category or as a new set of Rules of Origin.
What is the DGFT Open API Facility for Certificate of Origin?
An API is a controlled technical connection that allows two software systems to exchange information without a person having to enter the same data into each system manually.
For exporters, this means information already available in an ERP, accounting platform, or another compatible business system can be connected with DGFT's Certificate of Origin system.
Earlier, an exporter might have the required commercial or shipment information in its own software but still need to enter relevant CoO details separately on the DGFT platform. The new facility is intended to reduce that duplication.
The API does not create a new Certificate of Origin. It changes how eligible exporters and their systems can communicate with DGFT's CoO platform.
Why Has DGFT Introduced the Open API Facility?
The immediate issue addressed by the facility is repeated data entry.
Where businesses already maintain export information in an ERP or accounting system, entering the same details again creates extra work and increases the chance of typing mistakes.
DGFT identifies three clear operational benefits:
- electronic transfer of application data from exporter systems
- reduced repetitive data entry and
- reduction in errors, along with a quicker application workflow.
For businesses handling many export transactions, system-to-system transfer may also make internal processing easier because information can move through a more connected workflow.
That last point is a practical business implication, not a separate legal benefit announced by DGFT.
The Regulatory and Digital Trade Framework
The facility has been introduced by the Directorate General of Foreign Trade, which functions under the Ministry of Commerce and Industry.
The digital service operates through the Trade Connect e-Platform and relates specifically to the issuance and verification of Certificates of Origin.
A Certificate of Origin is used to establish the origin of exported goods for relevant trade purposes. Depending on the type of certificate and trade arrangement, origin can affect customs treatment in the importing country.
Three different official materials should not be confused:
- PIB announcement: Gives the main public explanation of the new facility.
- DGFT Trade Notice: Trade Notice No. 25/2026-27 dated 7 September 2026 contains the further official details referred to by PIB.
- Help manual: DGFT states that a step-by-step help manual has been annexed to the Trade Notice for the technical process.
What Has Changed for Certificate of Origin Applications?
The main change is the ability to transfer relevant application data electronically from an exporter's own system into DGFT's CoO system.
| Process Area | Earlier Position Described by DGFT | API-Enabled Position | Practical Meaning |
| Data entry | CoO information entered separately on DGFT platform | Information can be transferred less duplicate entry. electronically | Less duplicate entry |
| ERP/accounting data | Existing business-system data may need re-entry | System can connect with DGFT CoO system | Better system integration |
| Application exchange | Portal-based separate entry | CoO File API available | System-to-system exchange becomes possible. |
| Certificate receipt | Existing portal process | CoO File API can receive certificates | System-to-system exchange becomes possible. |
| Verification | Separate verification workflow | Certificate Verification API available | Issued CoOs can be verified electronically. |
| Tracking | Application status checked through system | Transaction ledger records application details | Better electronic visibility. |
The announcement does not state that every existing CoO filing route has been discontinued. Exporters should therefore avoid assuming that API integration has replaced all other processes unless DGFT expressly says so in the operative instructions.
Who Can Use the DGFT Open API Facility?
DGFT describes the facility as available to eligible exporters and their systems.
It is particularly relevant to exporters that already use:
- ERP systems
- accounting software or
- another business software capable of technical integration.
The PIB release itself does not provide a separate detailed eligibility matrix explaining every condition an exporter must meet before obtaining API access.
Businesses planning integration should therefore rely on the CoO Portal, Trade Notice, and official technical manual for the exact onboarding requirements.
How Does the DGFT Certificate of Origin API Work?
At a practical level, the new arrangement connects an exporter's business software with DGFT's CoO system.
The flow can broadly be understood as follows:
- Relevant CoO information exists in the exporter's ERP, accounting, or other business software.
- The exporter obtains API credentials through the API Management section of the CoO Portal.
- IP addresses from which the exporter's system will connect are registered.
- The Authentication Token API is used for secure access.
- The CoO File API supports submission of applications and receipt of certificates.
- DGFT processes the application through the CoO system.
- Application information can be monitored through the transaction ledger.
- Issued certificates can be checked through the Certificate Verification API.
These points describe the functional arrangement mentioned by DGFT. They should not be treated as a substitute for the detailed technical integration manual.
What are the Three APIs Introduced by DGFT?
DGFT has made three different APIs available. Each one has a separate function.
| API | Main Function | Exporter Use |
| Authentication Token API | Secure login/authentication | Establish authorised system access. |
| CoO File API | Application submission and certificate receipt | Exchange CoO files/data with DGFT |
| Certificate Verification API | Verification of issued certificates | Check an issued Certificate of Origin. |
Authentication Token API
This API controls secure access to the system.
An access token works like a temporary digital permission that allows an authorised system to communicate with the API. DGFT states that each access token remains valid for 60 minutes.
CoO File API
The CoO File API is used for submission of applications and receipt of certificates.
For exporters integrating ERP or accounting systems, this is the API most directly connected with the movement of CoO application information between the business system and DGFT.
Certificate Verification API
The Certificate Verification API is meant for verification of issued Certificates of Origin.
It should not be confused with issuance itself. Verification checks an issued certificate it does not mean every submitted application has been approved.
Preferential vs Non-Preferential Certificate of Origin Under the API Facility
DGFT's API facility supports both types.
| Particular | Preferential CoO | Non-Preferential CoO |
| Main purpose | Support preferential tariff treatment where applicable | Customs, compliance, trade remedy, and other trade purposes. |
| Trade agreement link | Normally linked with an applicable FTA, RTA or PTA | Not used to provide preferential tariff benefit. |
| Rules of Origin relevance | Yes, agreement-specific conditions apply | Origin certification is still relevant, but no preferential tariff benefit arises merely from the certificate. |
| Covered by DGFT API | Yes | Yes |
A Preferential CoO becomes commercially important where the importing country provides a tariff concession under an applicable trade agreement, and the exported goods meet the relevant origin conditions.
A Non-Preferential CoO serves other trade purposes but does not itself provide a preferential customs duty benefit.
Which Trade Agreements and Certification Schemes are Covered?
DGFT lists a broad group of agreements and certification schemes within the API framework.
| Agreement/Scheme | Type |
| India-Japan CEPA | Comprehensive Economic Partnership Agreement |
| India-Korea CEPA | Comprehensive Economic Partnership Agreement |
| SAFTA | Free Trade Arrangement |
| SAPTA | Preferential Trade Arrangement |
| ASEAN-India FTA | Free Trade Agreement |
| India-Singapore CECA | Comprehensive Economic Cooperation Agreement |
| India-Malaysia CECA | Comprehensive Economic Cooperation Agreement |
| India-Chile PTA | Preferential Trade Agreement |
| India-Mercosur PTA | Preferential Trade Agreement |
| India-UAE CEPA | Comprehensive Economic Partnership Agreement |
| India-Australia ECTA | Economic Cooperation and Trade Agreement |
| India-Oman CEPA | Comprehensive Economic Partnership Agreement |
| India-EFTA TEPA | Trade and Economic Partnership Agreement |
| India-UK CETA | Comprehensive Economic and Trade Agreement |
| Generalized System of Preferences | Certification scheme |
| Non-Preferential CoO Scheme | Non-preferential certification |
The inclusion of an agreement in the system does not mean every product automatically qualifies for preferential treatment. Product-specific and agreement-specific Rules of Origin still need to be satisfied.
How Does the System Apply Origin Criteria and Validation Rules?
DGFT states that the system automatically applies the relevant fields, origin criteria, and validation rules based on the agreement or certification scheme selected by the exporter.
This is useful because different trade agreements can require different information and origin conditions.
However, system validation and legal eligibility are not the same thing.
The exporter remains responsible for selecting the correct agreement and providing accurate information. Automation helps the filing system apply the relevant fields and validations, but it does not turn non-originating goods into originating goods.
System validation supports processing it does not replace the legal Rules of Origin applicable under the selected trade agreement.
How Can Exporters Obtain DGFT API Credentials?
DGFT states that exporters can obtain API credentials through the API Management section of the CoO Portal. They must also register the IP addresses from which their systems will connect.
An exporter considering integration should therefore first review whether its software is technically capable of communicating with the DGFT system.
The complete technical registration and authentication process is referenced on the Trade Connect e-Platform, while DGFT has also referred users to the step-by-step manual annexed to the Trade Notice.
Businesses should follow those official technical instructions rather than relying on a generic API setup process.
IP Allowlisting and Technical Connection Requirements
IP allowlisting is a security measure that allows connections only from approved IP addresses.
DGFT states that API access is restricted to IP addresses allowed by the exporter.
For a business, this means the IT or ERP team may need to identify the systems and network addresses that will communicate with DGFT.
This can involve coordination between:
- export documentation staff
- internal IT teams
- ERP administrators
- cybersecurity teams and
- third-party software providers.
These are practical implementation considerations. The PIB announcement does not turn every internal IT step into a separate statutory compliance requirement.
Security Features of the DGFT Certificate of Origin API
DGFT has provided fairly specific information on the security controls used in the Open API framework.
| Security Measure | Technical Detail | Main Purpose |
| Digital signature | SHA-256 RSA | Helps protect integrity and authenticate the sender. |
| Digital certificate | 2048-bit X.509 certificate | Supports trusted digital identification. |
| Password protection | PBKDF2 hashing | Protects stored password information |
| Salt | Dynamic salt | Makes password hashing harder to attack using repeated patterns |
| Network restriction | IP allowlisting | Restricts system access to approved IP addresses |
| Access token | Valid for 60 minutes | Limits the usable period of each authentication token |
DGFT states that requests and responses are digitally signed to support data integrity, sender authentication, and non-repudiation.
These safeguards reduce security risks, but they should not be described as making any digital system completely risk-free.
How Can Exporters Track CoO Applications Through the Transaction Ledger?
DGFT maintains a transaction ledger for each application. This gives exporters an electronic view of application progress and related reference information.
| Information | Recorded in Ledger |
| Draft | Yes |
| In Process | Yes |
| Approved | Yes |
| Certificate Issued | Yes |
| Rejected | Yes |
| Acknowledgement ID | Yes |
| File number | Yes |
| File date | Yes |
| Certificate number | Yes |
For businesses processing multiple export shipments, this can make internal follow-up easier because application and certificate references are available within an electronic transaction record.
DGFT's release does not separately define the legal meaning of every status, so businesses should avoid creating their own assumptions around rejection or approval stages.
What Technical Preparation May Exporters Need Before API Integration?
The following are sensible business preparations, rather than additional legal requirements announced in the PIB release.
Exporters considering integration may need to review whether their ERP or accounting software can support the DGFT API, identify where CoO-related information is stored, involve the internal IT team, and review the official integration documentation.
Data mapping may also need attention. If the field structure inside the business software does not match the information required by the CoO system, the ERP or software team may need to configure the exchange correctly.
Businesses should also identify the IP addresses that will be registered, decide who will control API credentials, and ensure export data is checked before it is transmitted.
Automation can reduce duplicate entry, but inaccurate source data can still result in an inaccurate application.
Role of Export, ERP, Accounting and IT Teams
Export Documentation Team
The export team remains responsible for the business information used in CoO applications and should make sure shipment and product details are consistent with supporting records.
ERP and IT Team
The technical team will be relevant for API authentication, software connection, IP configuration, and system-level data exchange.
Finance and Accounting Team
Commercial information already stored in accounting or business software may form part of the data flow. Coordination can reduce differences between internal records and the information submitted for export purposes.
Compliance and International Trade Team
The compliance team should continue to review the applicable trade agreement, origin requirements, and certification route. API integration does not remove the need for correct trade-compliance decisions.
Benefits of DGFT Open API for Exporters
The most direct benefits identified by DGFT relate to data handling.
Exporters can potentially avoid entering the same information repeatedly where that information already exists in compatible business software.
The new arrangement may provide:
- less duplicate data entry
- fewer avoidable manual-entry errors
- direct electronic data transfer
- closer integration between internal systems and DGFT
- electronic application tracking
- system-based receipt of certificates and
- electronic certificate verification.
DGFT expressly identifies reduced repetitive entry, reduced errors, and faster application processing as benefits of the facility.
These benefits should not be interpreted as guaranteed approval, zero errors, or guaranteed processing times.
Impact on MSME Exporters
For MSME exporters already using suitable accounting or ERP software, the API can reduce some of the administrative work involved in entering CoO information again on a separate system.
The benefit, however, will depend on the MSME's digital readiness.
A smaller exporter with limited internal IT capacity may need assistance from its software provider for API configuration. Businesses using basic systems may also need to assess whether integration makes commercial sense for their filing volume.
The announcement does not provide a separate MSME subsidy, exemption, or simplified API rule.
Its value for an MSME will therefore depend mainly on the exporter's own software setup and CoO workload.
Impact on Large Exporters and High-Volume Export Operations
Large exporters and businesses processing a high volume of Certificates of Origin may see a stronger operational case for integration.
Where the same information is already stored in an established ERP, reducing repeated entry across numerous applications can improve workflow efficiency.
Central application tracking can also help export departments monitor files, acknowledgement IDs, and certificate numbers more consistently.
These are practical benefits rather than guaranteed outcomes stated separately by DGFT. The actual value will depend on integration quality, internal controls and filing volume.
Is the DGFT Open API Mandatory for Exporters?
The PIB announcement does not describe the Open API as a compulsory system for every exporter.
Instead, DGFT states that the facility is now available for use by eligible exporters and their systems.
That distinction matters.
A Certificate of Origin may still be required depending on the export transaction, importing-country requirement, or preferential trade arrangement. But that does not automatically mean every exporter must adopt API integration.
The PIB release also does not state a compulsory migration date for all exporters.
Businesses should check Trade Notice No. 25/2026-27 and later DGFT instructions for any technical conditions applicable to their use of the facility.
Does the API Change Rules of Origin Requirements?
No change to the underlying Rules of Origin should be assumed merely because the application system is becoming more automated.
An API deals with how data is exchanged.
Rules of Origin deal with whether goods satisfy the origin conditions required under the relevant trade agreement.
These are different issues.
DGFT says the system applies relevant origin criteria and validation rules according to the agreement selected by the exporter.
An exporter must therefore continue to choose the correct agreement and satisfy the conditions applicable to the goods.
Does API Integration Guarantee Certificate of Origin Approval?
No.
Applying electronically through an API should not be treated as automatic approval.
DGFT itself lists several transaction-ledger statuses, including:
Draft โ In Process โ Approved โ Certificate Issued โ Rejected
The presence of both approval and rejection statuses makes it clear that submission and approval are separate stages.
The API changes how applications and certificates can move between systems. It does not remove the assessment or processing involved in CoO issuance.
What Has DGFT Not Expressly Specified in the Announcement?
Some information is not expressly stated in the PIB release.
| Matter | Position in PIB Release |
| Mandatory adoption deadline for all exporters | Not expressly specified |
| Separate API integration fee | Not expressly specified |
| Penalty for not using API | Not expressly specified |
| Full eligibility matrix | Not expressly specified |
| Complete technical configuration process | Referred to Trade Connect/manual |
| Discontinuation of every existing filing route | Not expressly specified |
| Guaranteed processing time | Not specified |
| Guaranteed CoO approval | Not provided |
This does not mean that no additional technical conditions exist elsewhere.
It simply means those details should not be invented from the press release. Exporters should refer to the DGFT Trade Notice and official help manual where more detailed implementation information is required.
Trade Notice No. 25/2026-27 and the DGFT Help Manual
PIB states that further information is available in Trade Notice No. 25/2026-27 dated 7 September 2026, issued by DGFT.
DGFT has also provided a step-by-step help manual annexed to the Trade Notice.
For an exporter or ERP team planning actual integration, this technical documentation is more important than relying only on the press announcement.
The press release explains what has been introduced. The Trade Notice and manual should be used for detailed registration, authentication, and integration steps.
DGFT Helpdesk and Official Support
DGFT has also kept an official support route open for stakeholders using the eCoO module.
The announcement specifically refers to:
- exporters
- Export Promotion Councils
- designated CoO issuing agencies and
- trade bodies.
These stakeholders may contact the DGFT Helpdesk through the available toll-free or email channels for queries, suggestions, and feedback relating to the eCoO module.
Impact on Exporters and Other Trade Stakeholders
| Stakeholder | Likely Impact | Main Concern |
| Exporters | Less repeated data entry | Data accuracy |
| MSME exporters | Easier digital workflow where systems support API | Technical readiness |
| Large exporters | Better integration for higher application volumes | System configuration |
| Export teams | More connected CoO workflow | Correct application data |
| ERP/IT teams | Direct role in API setup | Authentication and IP controls |
| Accounting teams | Existing business data may feed application workflow | Data consistency |
| CoO issuing agencies | Greater digital interaction | Process coordination |
| Export Promotion Councils | May assist with awareness and feedback | Exporter support |
The biggest change is that Certificate of Origin processing now becomes more closely connected with a company's own technology systems.
Challenges and Implementation Considerations
Initial Technical Integration
Businesses may need development or configuration work before an ERP can communicate correctly with DGFT's API.
Data Mapping
Fields in an internal system may need to match the format expected by the DGFT CoO system.
Cybersecurity Configuration
API credentials, digital signatures, access tokens, and IP addresses need proper handling.
Internal Coordination
An API project cannot be handled only by the export department. IT and compliance teams may also need to be involved.
Software-Vendor Dependence
Businesses using third-party ERP or accounting software may depend on their vendor for integration support.
Rules of Origin Accuracy
A technically successful application can still contain incorrect trade-compliance information. Exporters must continue to review the applicable agreement and origin criteria.
Is the DGFT Open API a Right Decision or an Additional Burden?
The change has clear operational advantages, but integration may also create some initial work for businesses.
| Positive Side | Possible Practical Burden |
| Reduces repetitive data entry | Initial API configuration |
| Can reduce manual-entry errors | ERP/vendor support may be needed |
| Enables direct system integration | IT resources required |
| Supports electronic application tracking | Staff may need familiarisation |
| Provides certificate verification API | Credentials need careful management |
| Uses defined security controls | IP and cybersecurity configuration required |
For exporters already working through structured ERP systems, the facility appears commercially useful because it reduces repeated data movement between internal software and DGFT.
For smaller businesses processing only limited CoO applications, the benefit may need to be weighed against the initial technical work involved.
The practical value will therefore depend on filing volume, software capability and internal IT resources.
Business Opportunities Created by DGFT CoO API Integration
The API facility may create additional demand around export-tech and compliance support.
Relevant areas can include ERP integration, API implementation, trade-document automation, Certificate of Origin documentation support, and Rules of Origin advisory.
Software companies serving exporters may also see greater demand for systems capable of interacting with government trade platforms.
From a compliance perspective, greater automation can increase the need for accurate source data. This keeps export documentation and Rules of Origin review relevant even when the method of submission becomes more digital.
What Exporters Should Do Next
Exporters considering the DGFT CoO API should follow a practical sequence:
- Check whether API integration is useful: Review the number of CoO applications handled and the systems currently used.
- Read the official Trade Notice and help manual: Technical implementation should be based on DGFT instructions.
- Assess ERP or accounting-software readiness: Confirm whether the current system can support integration.
- Review credential and IP requirements: Coordinate with the IT team before configuration.
- Check internal data quality: Information transferred automatically still needs to be accurate.
- Review Rules of Origin: Make sure the correct trade agreement and origin criteria are applied.
- Assign internal ownership: Export, compliance, and IT teams should know their responsibilities.
- Track DGFT updates: Further technical instructions or changes should be monitored.
There is no separate mandatory migration deadline stated in the PIB release, so businesses should avoid creating an artificial compliance deadline.
How Corpseed Can Help with Certificate of Origin and Export Compliance
Moving CoO applications into a more automated digital process does not remove the need for correct documentation and trade-compliance review. Exporters still need to identify the appropriate Certificate of Origin route, understand the relevant trade agreement, and maintain accurate supporting information.
Businesses looking for Certificate of Origin services in India can seek professional support where the trade or documentation position is unclear.
Certificate of Origin Support
Corpseed can assist exporters in understanding the relevant Certificate of Origin category and the documentation connected with the application.
Preferential and Non-Preferential CoO Guidance
Support can be provided in understanding whether a transaction relates to a Preferential or Non-Preferential Certificate of Origin.
Rules of Origin Review
Corpseed can assist exporters in reviewing the origin conditions applicable under the relevant trade agreement.
DGFT Compliance Support
Exporters can obtain support for relevant DGFT and foreign-trade compliance requirements connected with their transactions.
Export Documentation Review
Commercial and regulatory information can be reviewed for completeness and consistency before filing.
Trade Agreement Applicability Support
Businesses can obtain support in understanding which notified trade agreement may be relevant to a particular export transaction.
Compliance Gap Review
Missing, inconsistent, or incomplete records can be identified before they create problems during filing.
Ongoing Export Compliance Assistance
Businesses handling regular international trade may require continued support as DGFT procedures and digital systems change.
Corpseed does not control DGFT approval or guarantee Certificate of Origin issuance. The purpose of a Certificate of Origin consultant in India is to help businesses prepare and understand the compliance side of the process correctly.
Key Takeaways
- DGFT introduced the Open API facility for Certificate of Origin on 7 September 2026.
- Eligible exporters can connect ERP, accounting, or other business software with the CoO system.
- Both Preferential and Non-Preferential Certificates of Origin are covered.
- DGFT provides an Authentication Token API, CoO File API, and Certificate Verification API.
- Applications can be tracked through a transaction ledger.
- Security includes SHA-256 RSA digital signatures, 2048-bit X.509 certificates, PBKDF2 hashing, IP allow listing, and 60-minute access tokens.
- The API does not remove agreement-specific Rules of Origin requirements.
- The PIB release does not expressly prescribe a compulsory adoption deadline for all exporters.
The DGFT Open API for Certificate of Origin mainly changes the method of digital interaction between exporter systems and the CoO platform. Exporters still need accurate documentation and correct origin analysis behind that technology.
Schedule a Call Back
Document Preview
Embedded reference document
Related
Explore more updates from the same department.
