Enriched Ewb APIs#

APIs#

Headers#

Header Key Name	Description
Content-Type	It used to indicate the media type of the resource in the request for example: `application/json` for json document exchange
accept	It used to request the media type of the resource expected in the response for example: `application/json` for json document exchange
X-FLYNN-N-EWB-GSP-CODE	GSP Identifier: enum (“vay”)
X-FLYNN-N-EWB-GSTIN	GSTIN of the taxpayer
X-FLYNN-N-EWB-USERNAME	Portal username associated with taxpayer GSTIN for the GSP, Non-sensitive
X-FLYNN-N-EWB-PWD	Portal password associated with GSTIN and Username for the GSP, Non-Sensitive

Optionally if you want to encrypt the password you can use following headers instead of X-FLYNN-N-EWB-PWD

Header Key Name	Description
X-FLYNN-S-REK	Request Encryption Key - refer here optional, to be used when you want to encrypt the password
X-FLYNN-S-EWB-PWD	Portal password associated with GSTIN and Username for the GSP, Sensitive

With, addition to the headers described above also set all required headers to make an authenticated API call.

required headers for all EWB API calls

Content-Type
accept
X-FLYNN-N-ORG-ID
X-FLYNN-N-USER-TOKEN
X-FLYNN-N-EWB-GSP-CODE
X-FLYNN-N-EWB-GSTIN
X-FLYNN-N-EWB-USERNAME
X-FLYNN-S-EWB-PWD / X-FLYNN-N-EWB-PWD
X-FLYNN-S-REK (optional, use it in case if you wish to encrypt the password in the header)

Common Errors#

There could be multiple types of errors when interacting with enriched e-invoice APIs. However, the structure of the error payload would remain same.

For example, on submitting wrong document number, error given is error-code 206 which stands for invalid invoice number error.
check the full error list on Ewb Error list documentation page

Http Status Code: 400

{
  "data": [
    {
      "status": false,
      "error": {
        "message": "err-ewb-returned-error",
        "type": "eway-bill",
        "args": {
          "status": "0",
          "error-text": "{\"errorCodes\":\"206,\"}"
        }
      }
    }
  ]
}