EximFetch (a product of Brewcode Technologies Private Limited) sells a JSON API for Indian customs and trade reference data. This page states, in plain words, where every dataset comes from and how we collect it. The same statement is part of our Terms and conditions and Privacy policy.
Where the data comes from
Every dataset on EximFetch is taken from a document that a government body or a standards body publishes for anyone to read and download: a notification, a tariff schedule, a code directory, a rate list. These are public records. We add structure, history and an API on top of them; we do not create the underlying facts, and we do not take data from private, paid or login-protected sources.
- Central Board of Indirect Taxes and Customs (CBIC). Customs notifications, circulars and instructions, tariff schedules, tariff values and exchange-rate notifications published on the CBIC tax information portal.
- Indian Customs EDI Gateway (ICEGATE). The published directories of customs location, sea port, airport, airline, currency, country, state, package and unit codes, the customs exchange rates, the customs tariff with anti-dumping, countervailing, safeguard, drawback and preferential rates, and the public Shipping Bill enquiry.
- Directorate General of Foreign Trade (DGFT). The ITC-HS import and export schedules, policy conditions, scheme codes and the RoDTEP rate appendix.
- Financial Benchmarks India Limited (FBIL) and the Reserve Bank of India. Daily reference exchange rates.
- Goods and Services Tax Network (GSTN). State codes.
- India Code (Legislative Department, Government of India). The Customs Tariff Act schedules as consolidated.
- International Organization for Standardization (ISO). Country (ISO 3166) and currency (ISO 4217) code lists.
- GeoNames. Indian PIN codes and world administrative divisions, under the Creative Commons Attribution 4.0 licence, credited on every record.
EximFetch is not an authorised partner, affiliate, agent or representative of any of these bodies, and none of them endorses or certifies our service. The published document always prevails over our copy of it.
How we collect it
- We download published documents. On a fixed schedule (every four hours for customs exchange rates, daily for most code lists and notifications, weekly for duty schedules) our software fetches the current copy of each document in the form the publisher offers it: a PDF, an Excel or CSV file, or a published list. It uses the same public download links a person would click, and it downloads each document once per cycle.
- We parse it with our own algorithms. The downloaded document is read by software written and maintained by us, which turns the lines of the notification, schedule or directory into structured records (codes, descriptions, rates, dates, the notification number they come from). Every record carries the name of the source, the URL of the document and the time we read it.
- We do not scrape websites. We do not crawl sites, we do not copy web pages, their text or their design, we do not log in to any portal, we do not use anyone else's account, and we do not bypass CAPTCHAs, rate limits, access controls, paywalls or any other technical restriction. We collect nothing that is not in the published document itself. Where a publisher offers a list only through a public lookup page rather than a file (for example ICEGATE's code directories and its Shipping Bill enquiry), we request that public page the way its own form does, slowly, without logging in, and keep only the codes and statuses it returns.
- We keep the load light. Requests are spaced out and identified as ours, we honour robots.txt, the published terms of use of each portal and any rate limit a publisher sets, and the total traffic we place on any one portal stays well below that of a single person browsing it. If a publisher asks us to change how we read a document, or to stop, we comply.
- We keep the facts, and credit the source. We store the facts stated in the document together with its source and URL. Where we serve an official PDF (customs notifications) it is the publisher's own file, copied unchanged and labelled as such. We claim no rights in any government text; our rights are in our software, our data structures and the API.
Questions from publishers
If you publish one of the documents we read and want to ask about how we download it, correct how we credit it, or ask us to change or stop, write to contact@eximfetch.com. We answer within five working days and act on reasonable requests.