Access income-tax notice and proceeding information through the RPACPC ITR Notice API. Retrieve structured records associated with a taxpayer, including proceeding details, document identification numbers, issue dates, response-related fields, proceeding status indicators, and document download links where available.
Integrate income-tax notice information into your applications to support tax compliance workflows, document management, and internal review processes.
The ITR Notice API accepts authentication credentials and a consent indicator. The supplied response contains multiple proceeding records, with each record providing notice-related metadata and a document download link when available.
The response includes proceeding names, taxpayer identifiers, document references, issue dates, read-status indicators, submission-related fields, and document IDs.
The API response may include the following information, depending on the response received:
Retrieve proceeding names, types, descriptions, and reference identifiers.
Access document identification numbers and document reference IDs.
Retrieve the issue date associated with each returned proceeding record.
Access status and submission-related indicators returned by the source.
Access document IDs and download links when provided by the service.
Process multiple proceeding records returned in a single API response.
Integrate returned proceeding information into compatible applications and workflows.
Provide the required username, password, and consent indicator to initiate the request.
The configured service processes the request and retrieves available income tax proceeding information.
Receive structured response data containing available notice details, proceeding metadata, and document references.
Use the returned document ID and download link to access associated documents where available and authorized.
Use the returned information for tax review, proceeding tracking, compliance workflows, and document management.
| Parameter | Type | Description |
|---|---|---|
| username | String | Username or identifier required by the configured service. |
| password | String | Password required by the configured service. |
| consent | String | Consent indicator; the supplied example uses Y. |
{
"username": "YOUR_USERNAME",
"password": "YOUR_PASSWORD",
"consent": "Y"
}
| Field | Description |
|---|---|
| status | Overall response status returned by the API. |
| status_code | Status code returned by the service. |
| message | Response message. |
| billable | Billable indicator returned by the API. |
| error | Error information, or null in the supplied successful response. |
| data | Container holding the returned proceeding records. |
| proceeding_req_id | Proceeding request identifier. |
| proceeding_name | Name of the proceeding, such as Issue Letter in the supplied response. |
| pan | PAN associated with the returned record. |
| name_of_assesse | Taxpayer name returned by the service. |
| proceeding_type | Proceeding type code returned by the source. |
| document_identification_number | Document identification number associated with the record. |
| issued_on | Date on which the document or proceeding was issued, as returned by the source. |
| served_on | Service-date field; may be null. |
| response_due_date | Response due-date field; may be null. |
| document_reference_id | Document reference identifier. |
| proceeding_status | Proceeding status code returned by the source. |
| is_submitted | Submission indicator returned by the source. |
| read_flag | Read-status indicator returned by the source. |
| doc_id | Document identifier. |
| download_link | Link provided for document retrieval, when available. |
| request_id | Request identifier returned by the API. |
| sequence_id | Sequence identifier associated with the request. |
| request_time | Request timestamp. |
| response_time | Response timestamp. |
{
"status": "SUCCESS",
"status_code": "200",
"message": "Data fetch successfully",
"billable": "Y",
"error": null,
"data": {
"0": {
"header": {
"form_name": null
},
"messages": [],
"errors": [],
"header_seq_no": "SAMPLE_SEQUENCE",
"proceeding_req_id": "SAMPLE_PROCEEDING_ID",
"proceeding_name": "Issue Letter",
"pan": "SAMPLEPAN01",
"name_of_assesse": "Sample Taxpayer",
"financial_yr": "-1",
"proceeding_type": "ITBA",
"document_identification_number": "SAMPLE_DIN",
"description": "[ITBA]Issue Letter",
"issued_on": "15-04-2026",
"served_on": null,
"response_due_date": null,
"document_reference_id": "SAMPLE_DOCUMENT_REFERENCE",
"proceeding_status": "O",
"is_submitted": "N",
"read_flag": "N",
"doc_id": 123456789,
"download_link": "YOUR_DOCUMENT_DOWNLOAD_LINK"
}
},
"request_id": "YOUR_REQUEST_ID",
"sequence_id": "YOUR_SEQUENCE_ID",
"request_time": "2026-10-26T10:00:00.000Z",
"response_time": "2026-10-26T10:00:03.000Z"
}
The response uses numeric-string keys such as "0", "1", and "2" under data, as shown in the supplied sample. The example above illustrates one record only.
Retrieve available proceeding records to support internal tax-notice review and follow-up workflows.
Use document identifiers, reference IDs, and download links to associate retrieved documents with internal records.
Integrate returned proceeding information into existing finance, tax, or compliance applications.
Use available status, read, and submission indicators to support internal review processes. Validate the meaning of each source status code before using it to determine an action or deadline.
Consolidate returned proceeding details into internal dashboards or case-management systems, subject to your implementation and data-access permissions.
Common questions about the ITR Notice API — what it returns, how fast it is, and how to integrate.
Government ID Check API helps banks, FinTechs, and NBFCs streamline KYC with faster identity verification and reduced manual work.
Read More
Empower your applications with India's Enterprise Verification Intelligence Platform for faster, more reliable verification.