Your export desk, filing at scale, without the portal.
Hundreds of certificates a cycle, submitted from your own tools. JSON or Excel in, certificates out, with subsidiaries and divisions as separate entities under one account, each with its own DGFT connection.
When eBRCs stop being a task and become a workload.
Past a certain volume, filing certificates one screen at a time stops making sense. The eBRC API moves the work into the tools your desk already runs.
Submit filings from your own systems as JSON, one record or an array per call, or move whole ledgers through Excel. Your desk stops re-keying data into a portal.
Each company lives as its own entity under one account, with its own DGFT connection. Filings, certificates, and records stay separate, entity by entity.
Submit once, get a request ID, poll for status, download the PDF. The certificate is usually back in about two hours, and nothing about that contract changes week to week.
JSON or Excel in. Certificates out.
Filings originate from your own tools, not from a browser tab. Every submission returns a request ID you can poll, and you usually have the certificate back in about two hours.
One record or an array per call. Consistent JSON envelopes, stable machine-readable error codes, and a request ID on every response.
Download a pre-filled template, fill it, upload it back, .xlsx or .xls up to 5 MB. Bulk data exports back out as xlsx or CSV.
Validation errors name the row and the field, in plain terms, so your team fixes the file instead of guessing at a rejection.
You submit in minutes. The certificate is usually back in about two hours, and status is a poll away the whole time.
Sandbox first.
Live on your signature.
Four steps from first call to production, and nothing is legally binding until the last one.
Build in the sandbox
The sandbox is the default. Prove your format and mapping end to end, with real validations and nothing legally binding.
sandbox by defaultOnboard your entities
Create each subsidiary or division as an entity under your account. Each one connects its own DGFT account and files as itself.
multi-entitySubmit and poll
Push mappings as JSON, singly or in arrays, or upload the Excel template. Every submission returns a request ID you poll until the certificate is ready.
requestId on every callSign and go live
Production access follows an NDA and a production agreement, e-signed in the console. Every certificate records which environment produced it, so a rehearsal can never be mistaken for a legal filing.
e-signed in the consoleThe Excel path, for desks that live in spreadsheets
Not every volume desk wants to write code first. The template moves the same volume with no integration at all.
- Pre-filled to start. Download the template with the known columns already in place; your team adds the invoice detail.
- .xlsx or .xls, up to 5 MB per file.
- Errors come back per row, naming the field, so the fix is an edit, not an investigation.
- Bulk out, too. Export data back out as xlsx or CSV whenever your systems need it.
billNo: this field is required
currency: use the ISO code, e.g. USD
Boring where it should be. Documented where it counts.
The parts your engineers will actually ask about, stated plainly.
One header over HTTPS: x-api-key. Keys are issued per environment and shown once at issue. Keep yours safe; it can't be recovered later, only reissued.
Published per endpoint in the docs. The tightest sit on the endpoints that reach DGFT, so the service stays dependable for every desk.
List endpoints take page and limit, with limit capped at 100.
Consistent JSON envelopes with stable, machine-readable error codes, and a request ID echoed on every error. Quote it to support and the conversation starts with facts.
An OpenAPI spec, plus copy-paste cURL for every endpoint.
Purpose codes, currency codes, port codes, and field-by-field specs, kept in the docs where your team can find them.
Free for general use: 250 production certificates a month and up to 10 exporter entities, with sandbox use not metered. The full definition lives on the pricing page. For committed volume or customisation, send your requirement through the contact form and we will come back with a quote.
Your volume, allowance, and contracts, visible.
Certificates generated, success versus processing, the weekly trend, peak day, and daily average. You see the ceiling before you hit it.
How much of the monthly allowance remains, and how many days are left in the cycle, always visible.
View each key's environment, status, and creation date, and copy the one you need.
The NDA and production agreement are e-signed inside the console. Production access follows your signature, not a paper chase.
Rehearse in a real sandbox. Go live on your signature.
Build against a real sandbox first. Nothing is legally binding until you switch, the switch is explicit, and a rehearsal can never be mistaken for a legal filing.
Trust, stated plainly.
Every integration starts in the sandbox, live filing sits behind an explicit switch, and every certificate records which environment produced it.
Production access follows a signed NDA and production agreement, e-signed in the console. Rigour, not friction.
Validation runs before anything is filed, and errors name the row and the field, so a rejection is an edit, not an investigation.
You submit in minutes. The certificate is usually back in about two hours. We will never tell you otherwise.
Certificate PDFs, copyable eBRC numbers, and bulk exports out as xlsx or CSV, whenever your systems want them.
Write to us with a request ID and a real person replies, usually within a day. Support conversations start with facts, not screenshots of a portal.
Asked, answered.
Yes. The API holds many exporter entities under one account, each with its own DGFT connection. Subsidiaries and divisions file as themselves, and their records stay separate.
Every submission returns a request ID, and you poll a status endpoint until the certificate is ready. It is a simple, dependable contract.
Get started and build against the sandbox first. Production access follows an NDA and a production agreement, e-signed in the console, and every certificate records which environment produced it.
Direct Export, Softex, Service (Non-IT), and Deemed Export, with deductions for commission, discount, insurance, and freight, plus Vostro and third-party export cases.
It is free for general use: up to 250 production certificates a month and up to 10 exporter entities per account, with sandbox use not metered. For committed volume or customisation, write to us through the contact form with your requirement, and we will come back with a quote. The exporter app is a separate product and stays free forever.
Per-endpoint rate limits are published in the docs, with the tightest on the endpoints that reach DGFT. Every response carries a request ID you can quote to support.
Yes. Download a pre-filled template, fill it, and upload it back, .xlsx or .xls up to 5 MB per file. Validation errors come back per row, and bulk data exports back out as xlsx or CSV.
Not quite your shape?
File your own, in minutes of your time
Remittances arrive on their own and every certificate is a short submission away, with a Test mode so nothing is legally binding until you say so.
Get started →The API · For PlatformsCertificates as a feature of your product
Generating for your customers rather than your own entities? The same API serves every exporter on your platform, each filing as themselves.
Read the lifecycle →Guides · ResourcesThe eBRC, explained in plain English
Playbooks and guides on eBRCs, inward remittances, DGFT compliance, and the incentives that depend on realisation.
Read the guides →Talk to a human.
A question about certificates, the API, or a filing that will not behave: write to us and a real person replies, usually within a day.
- Exporters: stuck filings, missing IRMs, bulk uploads.
- Platforms and enterprises: API access, sandbox keys, and volume or customisation quotes.
- Anything else: we read everything that arrives.
Prefer email? amin@eximfiles.io
Hundreds of certificates a cycle, from your own tools.
Build against the sandbox today. Go live on your signature.