API Pricing Image

Overview

API to check the e-file status of your TDS return by taking in tan,form and job_id and getting their job status.

Problem

After posting a job using E-File TDS Return API, businesses would want to check their TDS filing status.

Solution

API provides the status of your TDS filing

Endpoint

HTTP Method	Resource
`GET`	/tds-compliance/tin-fc/deductors/{tan}/tdsrs/{form}/e-file

Request

Follow the below guidelines to pass the TAN & Job ID to check on your TDS filing status.

Path Parameter

Param	Type	Description	Example
tan	`string`	TAN of deductor	PDES03028F
form	`string`	TDS Return Form	26Q

Query Parameter

Param	Type	Description	Example
job_id	`string`	Job ID obtained from uploading the txt and csi file.	f24cd229-42c8-43de-af79-8ce2d3c4c3db

Sample CURL Request

curl --request GET \
     --url 'https://api.sandbox.co.in/tds-compliance/tinfc/deductors/PDES03028F/tdsrs/26Q/e-file?job_id=f24cd229-42c8-43de-af79-8ce2d3c4c3db' \
     --header 'Accept: application/json' \
     --header 'Authorization: xxxxxxxxxxxxxxxxx' \
     --header 'x-api-key: xxxxxxxxxxxxxxxx' \
     --header 'x-api-version: 1.0

Response

Param	Type	Description	Example
job_id	`string`	ID of the particular `txt` and `csi` uploaded. It will be used later on to check status.	f24cd229-42c8-43de-af79-8ce2d3c4c3db
status	`string`	The status the particular `fvu` upload. Possible Values: `JOBQUEUED` `JOBDONE` `JOBFAILED`	JOBQUEUED
message	`string`	Reason for not e-filing TDS return. Will be visible only when the status is `JOBFAILED` For possible values, refer to the Annexure - TIN FC	Regular Statement with the same TAN, Financial Year, FORM, and Quarter is already furnished
signed_url	`string`	Provides Acknowledgement of TDS Return. Will be visible only when the status is `JOBDONE`	https://...

Response Caching

Response caching is not available for this API. Learn more about our response caching mechanism here

Wallet Charges

Since Get E-File Status API is not a Paid API, no wallet charge will take place.

Versioning

The API is currently in major version 2.0. Refer to the below table for the versioning history of this API along with the Changelog.

Version	Description	Link to the endpoint
2.0	Inclusion of form type in the path parameter.
1.0	This is the first version of the API.

Refer to our versioning policies here