Eway Bill latest release notes.

[Chartered Information Systems Pvt. Ltd.]

Dear ASP's:

Changes in 1.03 Version (dt:05.04.2021)

• Authentication: New authentication API has been released with end point as The request payload has been changed, complete payload needs to be encrypted using the public key. Click here for details of the API. The old authentication API is deprecated, will be removed shortly
  
  
• Generation of E Way Bill: Following validations have been added / updated
  • There should be at least one item with HSN code (goods). E Way Bill cannot be generated with documents having only SAC code (services)
  • PIN code 999999 is allowed for state code 97 (Other territory)
  • If the ‘TransMode’ is ‘4’ (Ship), then ‘VehicleType’ can be ‘O’ (ODC)
    
    
• Get E Way Bills for transportation: New API has been provided for transporters to download the E Way Bills assigned to them by passing their state code and data of assignment of E Way Bill. Click here for the API details
• If Mode transportation is selected has ship, the vehicle type can be ODC and Vehicle Number has to be provided
• UQC Code while Initializing multi-vehicle movement UQC value is not validating against the UQC provided while generating E-waybill
  
  For more details refer below link
  
  https://docs.ewaybillgst.gov.in/apidocs/
  
  
• Authentication changes shall be transparent to users of TaxPro EWB libraries or Decrypted (url based) API.
• The changes shall be released in Sandbox shortly and will be notified in TaxPro GSP Google Group.
  
  

  Other Important Note From TaxPro GSP:
  

  1. New eInvoice auth API v1.4 is now available in Sandbox http://gstsandbox.charteredinfo.com  (as per Release Notes (einv-apisandbox.nic.in)

  2. Start using https://einvapi.charteredinfo.com for EWB, eInvoice, and ASP Api at the earliest opportunity.

  3. Please make sure you are passing Header "Content-Type" : "application/json" in ALL post requests.

  4. No need to pass Accept: application/json header. Remove the Accept header if it’s adding escape chars (\) to response Json.

  5. Old sandbox at http(s)://testapi.taxprogsp.co.in is deprecated and is mapped to http(s)://gstsandbox.charteredinfo.com as of now until it would be phased out in couple of months.

  6. It's suggested that SAP users enable SNI so that they will not face TLS certificate issues... https://answers.sap.com/questions/599994/ssslerrservercertmismatch.html
  
  Warm Regards,
  TaxPro GSP Team.

[bkv...@gmail.com]

Message from NIC:

The changes implemented in the sandbox  (dated 05/04/2021) are being deployed on the production.

These changes mainly are related to enhanced validations and new APIs.

Old authentication API will be available for a couple of days on production, once the new version is released.

You are requested to migrate to the new authentication API at the earliest.

Comments from TaxPro GSP:

1. EWB Authentication API changes released in Sandbox https://gstsandbox.charteredinfo.com and Production https://einvapi.charteredinfo.com

2. The only change for Decrypted API users is: change /authenticate to /auth in Authentication url
ex:  Old Url: 
        New Url: 

3. Changes will not be released on old platform http(s)://api.taxprogsp.co.in
ASPs are requested to test on http(s)://gstsandbox.charteredinfo.com and migrate production to http(s)://einvapi.charteredinfo.com

4. EWB Library Version 2.2 released for Authentication API changes and is available for download.  

Warm Regards
TaxPro GSP Team

[bkv...@gmail.com]

Example Urls:
Old Url:  https://gstsandbox.charteredinfo.com/ewaybillapi/dec/v1.03/authenticate?&action=ACCESSTOKEN&aspid=xxxxxxxxxx&password=xxxxxxxxxxxx&gstin=34AACCC1596Q002&username=TaxProEnvPON&ewbpwd=abc34*

New Url: https://gstsandbox.charteredinfo.com/ewaybillapi/dec/v1.03/auth?&action=ACCESSTOKEN&aspid=xxxxxxxxxxxxx&password=xxxxxxxxxx&gstin=34AACCC1596Q002&username=TaxProEnvPON&ewbpwd=abc34*