Contract changed for TDSR E-File API

Contract Changed: TDSR E-file APIs using TXT & CSI File
Contract Changed: TDSR E-file APIs using FVU & Form27A

TDSR E-file API using TXT & CSI file

The API has minor changes in the endpoint and response structure. Note that the changes are in immediate effect.

Users will still be able to hit the previous version of the API until 29th February 2024

New Endpoint

Previous	New
/tds-compliance/tin-fc/deductors/:tan/tdsrs/:form/e-file	/tds/compliance/tin-fc/deductors/:tan/tdsrs/:form/e-file

Changes in the API response structure

The API response will now include the @entity and status key. A sample payload can be seen below:

{
  "code": 200,
  "timestamp": 1616223781341,
  "transaction_id": "fd096e71-faa0-419b-9133-85f53ca658d7",
  "data": {
    "job_id": "096c4812-1829-4ee1-a3c6-3bd291654b72",
    "status": "succeeded",
    "receipt_url": "https://s3.ap-south-1.amazonaws.com/efile.tds-compliance.sandbox.co.in/receipt.pdf",
    "fvu_url": "https://s3.ap-south-1.amazonaws.com/efile.tds-compliance.sandbox.co.in/fvu.fvu",
    "form27a_url": "https://s3.ap-south-1.amazonaws.com/efile.tds-compliance.sandbox.co.in/form27a.pdf"
  }
}

Furthermore, the job status enumerations have changed:

Previous	New
JOBCREATED	created
JOBQUEUED	queued
JOBDONE	succeeded
JOBFAILED	failed

You can refer to the updated API documentation for Submitand Poll Job APIs

TDSR E-file API using FVU & Form27A