Skip to main content
GET
Get E-Invoice by IRN

NIC validations

  1. IRN can be retrieved using this API within three days from the date of generation of IRN.
  2. If e-commerce wants to Get the RCM Invoice details, in the headers the supplier GSTIN value should be the Recipient GSTIN.

Response schema

For successful responses, this resource describes the NIC payload at data.Data.

View JSON schema

Authorizations

authorization
string
header
required

E-invoice taxpayer access token returned by Authenticate.

x-api-key
string
header
required

Sandbox API key from your Sandbox account.

Headers

x-source
enum<string>
default:primary

NIC server for the session used by this request. primary selects NIC1. secondary selects NIC2. Defaults to primary. See NIC1 and NIC2 routing.

Available options:
primary,
secondary
Example:

"primary"

x-proxy
enum<string>

NIC server that receives the request. If omitted, the request goes to the server selected by x-source. When specified, selects the other server. See NIC1 and NIC2 routing.

Available options:
primary,
secondary
Example:

"secondary"

x-api-version
string
default:1.0.0

API version

Path Parameters

irn
string
required

Query Parameters

supplier_gstin
string

Supplier GSTIN when an e-commerce operator acts on behalf of the supplier. For reverse charge mechanism (RCM) invoices, this is the recipient GSTIN.

Response

200 - application/json

2148 IRN data not available / 2283 IRN generated more than 2 days ago / 200 Get cancelled IRN / 200 Get IRN (DBN) / 200 Get IRN (CRN) / 200 Get IRN (INV)

A successful NIC response or a NIC business-error response. Both variants use HTTP 200.

code
enum<integer>
required

HTTP-compatible Sandbox response code.

Available options:
200
Example:

200

timestamp
integer<int64>
required

Unix timestamp in milliseconds.

Example:

1763446641000

transaction_id
string
required

Request transaction identifier.

Example:

"175fe134-c501-4ac0-8403-b52a4abccd0b"

data
object
required