E-invoice API Invocation
When you invoke E-invoice API you need to take care of populating the headers correctly, creating the request payload, encrypting the payload and wrapping it in an envelope and then processing the responses (which usually require further decryption activities).
We are demonstrating 3 sample call logs (1 authentication, 1 for a post and 1 for a get) for your review to understand what the request / response payloads will look like
But before that, you will be required to encrypt some files during authentication with the NIC public key. Please note below the correct public key to use.
- Sandbox NIC Public Key for Encryption of Password and App Key for Authentication
-
Production NIC Public Key for Encryption of Password and App Key for Authentication
- Production NIC Public Key for verification of signed content
- Production NIC 2 Public Key for verification of signed content
Let us start with a sample call to authentication.
IMPORTANT NOTIFICATION#
NIC has released a notification where NIC will be blocking the Users calling large number of erroneous hits to the GST E-Way Bill and GST eInvoice Systems.
In case of any error due to validation or data of data type or format or otherwise, appropriate error codes and error messages are provided in response to such requests by the GST system. The taxpayer application has to capture these error codes and facilitate taking action in correcting the issue and only then re-send the requests.
We request you to please refer https://einvoice1.gst.gov.in/Others/ResolutionErrors for Resolution on Common Errors provided by NIC.
Request you to please restrict the repeated erroneous API calls to E-Way Bill and eInvoice Systems.