FousDGFT portal
Pull your DGFT IRMs and eBRCs into your own systems
Read the IRMs on your IEC, your eBRC repository and the status of your submitted applications on the DGFT portal with one API call each. Or have a workflow check the IRM/ORM Repository every weekday morning and email you the IRMs it did not see the day before.
Works with your own DGFT portal account. Fous is an independent product.
What you can build on the DGFT portal
Get IRMs from the IRM/ORM Repository
Build thisSearches Inward Remittance in the IRM/ORM Repository under Services > eBRC for your IEC and reads each IRM with its bank's IFSC code, amount and purpose code.
- Takes
- From date, to date
- Returns
- IRM number, IRM issue date, IRM status, IFSC code, remittance date, currency, amount, remitter name, remitter country, purpose code
Search the eBRC repository
Build thisReads My Dashboard > Repository with bill type e-BRC: each Bank Realisation number with its shipping bill and its Bank Realisation and Utilisation status.
- Takes
- BRC issue from date, BRC issue to date, shipping bill number (optional)
- Returns
- Bank Realisation number, BRC issue date, date realised, FOB value realised, Bill ID, shipping bill number, date and port, Bank Realisation status, Utilisation status
Track submitted applications
Build thisSearches My Dashboard > Submitted Applications by scheme and sub-scheme and reads each application's status, such as In Progress, Deficient or Approved.
- Takes
- Scheme, sub-scheme, from date, to date
- Returns
- Application number, file number, sub-scheme, branch, status, deficiency issue date, RA office
Generate an eBRC from IRMs
Build thisFills the Generate e-BRC form under Services > eBRC: the IRMs and amounts, then the shipping bill or invoice details, and generates the eBRC.
- Takes
- eBRC type, IRM numbers and amounts, AD code, shipping bill or invoice number, date, port code, currency, value
- Returns
- eBRC number, IRM numbers, FOB value realised, net realised value
Automate the DGFT portal with a workflow
A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.
New IRMs on your IEC, every weekday
Build this- Starts
- Every weekday at 9:00, India time
- Step 1
- Get the IRMs from the IRM/ORM Repository for the last 30 days.
- Step 2
- Keep the IRMs that were not there on the last run.
- Step 3
- Email you the list with IRM number, bank IFSC, remittance date, currency, amount and purpose code.
Last week's eBRCs, handed to accounting
Build this- Starts
- Every Monday at 8:00, India time
- Step 1
- Search the eBRC repository for eBRCs issued in the last 7 days.
- Step 2
- Stop when there are none.
- Step 3
- Post each eBRC's number, shipping bill, FOB value realised and Utilisation status to your accounting webhook.
Applications that turned Deficient
Build this- Starts
- Every weekday at 17:00, India time
- Step 1
- Track the submitted applications for each scheme you name, for the last 90 days.
- Step 2
- Keep the applications whose status changed to Deficient since the last run.
- Step 3
- Email you each one with its application number, file number, deficiency issue date and RA office.
You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.
Once built, one call from your code
Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get IRMs from the IRM/ORM Repository” would look like.
curl https://api.fous.com/v1/runs \
-H "Authorization: Bearer $FOUS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"method": "dgft.gov.in/get_irms",
"input": {
"from_date": "2026-10-13",
"to_date": "2026-11-12"
}
}'
{
"status": "completed",
"data": {
"iec": "0512345678",
"irms": [
{
"irm_number": "ACMEB0251110000437",
"irm_issue_date": "2026-11-10",
"irm_status": "Fresh",
"ifsc_code": "ACME0001204",
"remittance_date": "2026-11-07",
"currency": "USD",
"amount": 18450,
"remitter_name": "Northwind Traders",
"remitter_country": "US",
"purpose_code": "P0102"
}
],
"count": 1
}
}
An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.
The DGFT portal’s own options
DGFT publishes an eBRC API for IEC holders and the technical partners they authorise. It fetches IRMs, ORMs and eBRCs and generates eBRCs in bulk, from a whitelisted IP with encrypted, signed messages. IEC profile, authorisation and other applications are made on the portal itself.
| Option | What it covers | What it takes |
|---|---|---|
| eBRC API | Fetch IRM and ORM details, push invoice and IRM mappings to generate eBRCs in bulk, get the processing status and fetch eBRC details. | A portal user linked to the IEC, eBRC access granted by the IEC user, a credential file valid 1 year, a whitelisted public IP, encrypted signed payloads. |
| Bulk tools on the portal | Bulk Generate eBRC, Bulk Download of IRMs, ORMs and eBRCs, and the IRM Utilization Report as an Excel file. | A portal login with the IEC linked. The IRM Utilization Report is generated by a batch and sent by email. |
| The DGFT portal by hand | IEC Profile Management, eBRC, authorisation applications and My Dashboard > Submitted Applications. | A registered user linked to an IEC. Filings are signed with a DSC or Aadhaar e-Sign. |
Read on November 12, 2026: Electronic Bank Realisation Certificate (eBRC), DGFT eBRC IEC Integration System Technical Specs v1.3, DGFT Public API Management for Exporters.
Signing in to the DGFT portal
The DGFT portal signs you in with your registered email ID as the username and a password. Registration checks codes sent to your email and mobile, and filings such as cancelling an eBRC are signed with a DSC or Aadhaar e-Sign. With Fous you sign in once through the portal's own sign-in with your own account, the login is sealed with AES-256, and an expired session is signed back in.
Worth knowing
- What can be clubbed in one eBRC
- IRMs can be clubbed only when they share a currency and the same bank name and account number. The manual's clubbing rules exclude purpose codes P0101 and P0108.
- The eBRC API answers hours later
- A bulk eBRC request is validated first and processed later. The specification asks for a gap of 2 hours between the push and the status call, and its introduction says 4 hours.
- API credentials expire after a year
- The credential file downloads once and is valid for 1 year. Calls are accepted only from the public IP you registered, and a new IP added in production works after 24 hours.
- Only your own unused eBRCs can be cancelled
- An eBRC uploaded by a bank cannot be cancelled. A self-certified one can, if it has not been utilised, with a 250-character remark and a DSC or Aadhaar e-Sign.
More in Logistics: forwarders, air cargo and customs
- Extensiv 3PL Warehouse Manager
- Air France KLM Martinair Cargo myCargo
- e-SkyCargo
- Lufthansa Cargo eServices
- ACE Secure Data Portal
- CARM Client Portal
- Dubai Trade
- Customs Declaration Service
- douane.gouv.fr
- ACE AESDirect
- myDHLi
- myDSV
- myKN
- IPAFFS
Other industries: LPL ClientWorks, DAKOSY, CassPort, TWX-21, ABS MyFreedom, PropertyMe.
Frequently asked questions
Yes: DGFT's eBRC API. It fetches IRMs, ORMs and eBRCs and generates eBRCs in bulk for an IEC, once the IEC user grants eBRC access, you generate a credential file and you register your public IP. IEC profile updates and authorisation applications are made on the portal.
Yes. In the IRM/ORM Repository, set the filters and select Request Bulk Download IRM/ORM, or use Bulk Download Request under eBRC. The IRM Utilization Report is a separate batch report: it shows Submitted, Processed or Failed and is sent by email.
Usually because they differ in currency, bank or account. Only IRMs of the same currency and the same bank name and account number can be clubbed, and P0103 is the purpose code that can be combined with another.
In My Dashboard > Repository with bill type e-BRC. Each result shows the Bank Realisation status and the Utilisation status, with the shipping bill number, date and port.
No. Fous is an independent product. You use it with your own DGFT portal account, and a method reads and does only what that account can.
Put DGFT portal behind an API call
Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Read nextExtensiv 3PL Warehouse ManagerAir France KLM Martinair Cargo myCargoe-SkyCargoLPL ClientWorksHow methods workHow workflows run
Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of DGFT portal (Directorate General of Foreign Trade, India). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.