Diagnostic microcuvette classification follows sole-use analytical function, placing specialised disposable cuvettes with their analyser rather than g...
Customs Broker licensing proceedings fail when their offence-report foundation collapses and authorisation, advisory, and KYC duties remain unbreached...
Tariff classification of Digital Axle Counters affirmed as electro-mechanical railway signalling equipment, eliminating duty, confiscation and penalty...
Open API integration on the Trade Connect e-Platform enables...
Certificate of Origin API integration enables secure electronic applications, agreement-specific validation, certificate issuance and online authenticity verification for exporters.
Contents
Summary
Note
Bookmark
Share
✓ Copied successfully !
Print
Print Options
For full text, please login
Login to TaxTMI
Verification Pending
The Email Id has not been verified. Click on the link we have sent on
Open API integration on the Trade Connect e-Platform enables eligible exporters to connect ERP, accounting and other systems with the Certificate of Origin process for electronic application submission, certificate issuance and verification. DGFT prescribes onboarding credentials, public-IP whitelisting, PBKDF2 password protection, token-based authentication and digital signing of requests and responses using SHA-256 RSA signatures and 2048-bit X.509 certificates. Access tokens may be reused during their 60-minute validity. Exporters must submit prescribed applicant, certificate, invoice, product, shipment, supporting-document and declaration data through the CoO File API, with agreement-specific validation of origin criteria and shipment requirements. The facility covers preferential and non-preferential certificates, while the Verification API confirms certificate validity and provides the certificate PDF URL and remarks.
Open API integration on the Trade Connect e-Platform enables eligible exporters to connect ERP, accounting and other systems with the Certificate of Origin process for electronic application submission, certificate issuance and verification. DGFT prescribes onboarding credentials, public-IP whitelisting, PBKDF2 password protection, token-based authentication and digital signing of requests and responses using SHA-256 RSA signatures and 2048-bit X.509 certificates. Access tokens may be reused during their 60-minute validity. Exporters must submit prescribed applicant, certificate, invoice, product, shipment, supporting-document and declaration data through the CoO File API, with agreement-specific validation of origin criteria and shipment requirements. The facility covers preferential and non-preferential certificates, while the Verification API confirms certificate validity and provides the certificate PDF URL and remarks.
Note: It is a system-generated summary and is for quick reference only.