Parent API: GST API Quickstart guide Authentication guide

File GSTR-1 Return with EVC

Q: What parameters and payload format are required for File GSTR1 data?

Requests are submitted via HTTP POST to '/gstr1/retevcfile'. Required parameters: 'email' (query parameter), 'pan' (query parameter), 'evcotp' (query parameter), 'gstin' (header parameter), 'ret_period' (header parameter), 'gst_username' (header parameter), 'state_cd' (header parameter), 'ip_address' (header parameter), 'txn' (header parameter), 'client_id' (header parameter), 'client_secret' (header parameter). A JSON request body ('Content-Type: application/json') is accepted per the schema specifications shown in the request documentation.

Q: What response status codes and format does File GSTR1 data return?

For File GSTR1 data (POST '/gstr1/retevcfile'), responses are returned in JSON format ('application/json'). Documented response codes in the specification include: HTTP 404 (Not Found. If requested entity is not found or if requested API is not found.), HTTP 500 (Internal server error).

POSThttps://apisandbox.whitebooks.in/gstr1/retevcfile

Used to file entire GSTR1 invoices using EVC.

1-Click Filing Engine

Explore Feature

Automated GSTR-1 Filing with DSC & EVC

Review final return totals, auto-trigger Aadhaar/mobile OTP or Digital Signature (DSC) authentication, and receive an instant ARN confirmation.

Parameters

query parameters

emailstringrequired

API Developer User Email

panstringrequired

PAN Number

evcotpstringrequired

OTP for EVC

header parameters

gstinstringrequired

GST Number

ret_periodstringrequired

Return Period (MMYYYY)

gst_usernamestringrequired

GST UserName

state_cdstringrequired

State Code

ip_addressstringrequired

IP Address

txnstringrequired

Transaction

client_idstringrequired

Client ID

client_secretstringrequired

Client Secret

Request Body

application/jsonrequired

any

Response

Not Found. If requested entity is not found or if requested API is not found.

Frequently Asked Questions

Requests are submitted via HTTP POST to /gstr1/retevcfile. Required parameters: email (query parameter), pan (query parameter), evcotp (query parameter), gstin (header parameter), ret_period (header parameter), gst_username (header parameter), state_cd (header parameter), ip_address (header parameter), txn (header parameter), client_id (header parameter), client_secret (header parameter). A JSON request body (Content-Type: application/json) is accepted per the schema specifications shown in the request documentation.

For File GSTR1 data (POST /gstr1/retevcfile), responses are returned in JSON format (application/json). Documented response codes in the specification include: HTTP 404 (Not Found. If requested entity is not found or if requested API is not found.), HTTP 500 (Internal server error).

Used to file entire GSTR1 invoices using EVC.

File GSTR1 data

Get TXPA

POST/gstr1/retevcfile

1const response = await fetch('https://apisandbox.whitebooks.in/gstr1/retevcfile?email=value&pan=value&evcotp=value', {

2 method: 'POST',

3 headers: {

4 gstin: "value",

5 ret_period: "value",

6 gst_username: "value",

7 state_cd: "value",

8 ip_address: "value",

9 txn: "value",

10 client_id: "value",

11 client_secret: "value",

12 Content-Type: "application/json"

13},

14 body: JSON.stringify({}),

15});

17const data = await response.json();

18console.log(data);

No example available.