New eInvoice API Version 1.01 (Beta) is available in sandbox for testing.

[Chartered Information Systems Pvt. Ltd.]

Dear ASP / TaxPayer:

Greetings form TaxProGSP !!

Please refer to Annexure indicating changes in eInvoice API in version 1.01 received from GSTN at the bottom of this post.

The response model in new version, (especially “InfoDtls” element) is fairly standard, elaborate and accommodative of future changes.  We have deduced that “InfoDtls” element may be present even in case API is successful and may contain multiple occurrence (array) of different “InfCd”.

There are notable changes in Generate IRN Request payload. Please refer to help or sample source code of integration project.

EWB details fields “EwbNo”, “EwbDt”, “EwbValidTill” added to Generate IRN Response models. (Shall work form 15th March, 2020 as per remark in GSTN note.)

Thus upgrade to this version are breaking changes for API and ASPs need to rework to handle response models.

In Decrypted APIs also, we are passing the response in same form as received from Invoice Registration Portal (NIC IRP). Only we have added our fields viz. “ExtractedSignedInvoiceData”, “ExtractedSignedQrCode”, “QrcodeImage” (Base64) to provide you Decrypted (Extracted) Invoice data, Extracted QR Code content and QRCode image in Base64 string respectively.

Unlike shown in response model “Status”: “x” ; we found that Status is still integer and we are getting “Status”:0 or “Status:1  (not ‘0’ or ‘1’ as shown in GSTN’s eMail)

The users of 

a. Pass Through Encrypted API, 

b. Pass Through Decrypted API,

c. .NET or Java library;

all may refer to code in Sample Integration Project to check the possible ways to handle multiple types in InfoDtls or write their own code to use required part of InfoDtls as per their need.

GSP Error and IRP error may be differentiated by checking for “status_cd”:”0” in case of GSP Error and “Status”:0 in case of IRP Error.

In summary, there are Breaking changes as compared to previous version.  ASPs need to replace Url Route segment /api/ by version as /v1.01/ and keenly study the changes before embarking on the development.

PS: Documentation at https://help.taxprogsp.co.in/e-invoice is being updated and would be completed by tomorrow.

Details of urls and models for decrypted API shall be available at https://help.taxprogsp.co.in/e-invoice/decrypted_api.htm by tomorrow afternoon.

                                                Annexure – eInvoice ver 1.01 release notes from GSTIN

The E Invoice APIs as per the E Invoice registration schema published recently at the GSTN Portal are released as version 1.01.

The technical details for the APIs are made available in the portal https://einv-apisandbox.nic.in for the users to make changes in the consuming applications accordingly.

The APIs of Version 1.01 are now available for testing and the URLs of these APIs are available in the developer portal after login.

Following is the release note for the version 1.01

1. API version number is part of the URL. 

2. Generate IRN request payload will be as per the latest schema published by GSTN. 

3. The response for ‘Generate IRN’ API will have additional attributes "EwbNo","EwbDt", "EwbValidTill"

4. The response JSON structure will be as follows 

   {       "Status": "x",      "Data": <Encrypted Data>,      "ErrorDetails":"<Errors JSON>",      "InfoDtls": "<alert message>"  }                    

"Status" will be '0' for failure, '1' for success, If success, "Data" will have values, if failure, "ErrorDetails" will have values. Any additional information, will be provided through "InfoDtls" as follows. 

a. If the Generate IRN is called with same document details more than once, the "InfoDtls" will have an object as follows. 

"InfoDtls": [{  "InfCd": "DUPIRN",  "Desc": {  "AckNo": 12100028671,  "AckDt": "2020-02-29 14:51:00",  "Irn": "bc368ad93c9fa76a40167f2e16190dc56c93e6c0caf0d0a65c0a8317c9b19f4a"  }  }]  

b. If the Generate IRN request has details related to E Way Bill generation and if the E Way Bill could not be generated, the "InfoDtls" will have an object as follows. 

"InfoDtls": [{  "InfCd": "EWBERR",  "Desc": [{  "ErrorCode": "110",  "ErrorMessage": "Invalid Client-ID/Client-Secret"  }]  }]  

c. If any other information to be shared in response, the "InfoDtls" attribute will have the following object. 

"InfoDtls": [{  "InfCd": "ADDNLNFO",  "Desc": "<Any information to be shared>"  }]  

5. New validations are being applied on the IRN generation. Consuming applications are supposed to prepare the payload as per the validations and send the request payload. Validations at the IRP will be implemented in a phased manner.

6. Mapping of technical and JSON attribute names for IRN is provided in the portal.

7. API Specifications for Generation of E Way Bill for a given IRN is provided. (will be operational from 15/03/2020).

8. Generation of E Way Bill as part of IRN registration will be operational from 15/03/2020.

9. GetGSTINDetails API is enabled.

10. "ErrorDetails" and the "InfoDtls" will be in plain text and not as Base64 encoded format as mentioned in earlier documentation.

Thanks & Regards

TaxPro GSP