Skip to main content
POST
Submit IRMs for eBRC generation
Submit one or more IRM-to-invoice mappings for eBRC generation. You get back a DGFT acknowledgement with a requestId; keep it and poll status. Limited to 10 calls per minute.
Available in Production and Sandbox. In Production, acknowledgement typically arrives within about 2 hours.
See the full field list and constraints in the Push IRM Request Fields annexure. Dates are DDMMYYYY strings. The message-level uploadType is a string code and the item-level one is a number: 101 Direct Export, 102 Softex, 103 Service Non IT, 104 Deemed.

Request body example

recordResCount must equal the number of entries in ebrcBulkGenDtos. decalarationFlag keeps its wire spelling (as per DGFT specification). When isGstAvail is "Y", gstinInvoiceNumber and gstinInvoiceDate become mandatory; when "N", they must be null.

Response example

ackStatus values

Errors

Valid codes

Next steps

Authorizations

x-api-key
string
header
required

Body

application/json
platformCustomerId
string
required
recordResCount
number
required
uploadType
string
required

eBRC type code as a string: "101" Direct Export, "102" Softex, "103" Service Non IT, "104" Deemed.

decalarationFlag
string
required

Exporter declaration flag, Y or N (spelling as per DGFT specification).

ebrcBulkGenDtos
object[]
required

Response

Acknowledgement with DGFT Ack Id

dgftAckId
string
requestId
string
ackStatus
enum<string>

Push acknowledgement status

Available options:
Validated,
Failed
recordResCount
number
errorDetails
object[]