GSTR-2A API
GSTR-2A is an auto-drafted inward supplies statement on the GST portal that reflects documents uploaded by suppliers for a return period. Use these APIs to retrieve GSTR-2A documents (B2B invoices, credit/debit notes, ISD, imports, TDS/TCS, amendments) to reconcile purchase data and monitor Input Tax Credit (ITC).Section-wise inward documents
Retrieve B2B invoices, credit/debit notes, ISD credits, imports (IMPG/IMPGSEZ), and TDS/TCS deductions from suppliers.
Amendment visibility
Track supplier amendments with B2BA, CDNA, ECOMA endpoints and view change history through AMDHIST.
Reconciliation-ready outputs
Normalize inward supply data to match purchase registers and vendor records.
Compliance-safe access
Access GSTR-2A through authenticated taxpayer sessions.
How it works
Authenticate taxpayer
Call Generate OTP and Verify OTP to start a taxpayer session valid for 6 hours.
Create or refresh session
Use the session token for all GSTR-2A calls and refresh it with Refresh Session for long-running pulls.
Normalize and store results
Process the retrieved data for reconciliation against purchase records and audit trails.
API categories
Core invoices
B2B and B2BA endpoints for supplier invoices and amendments
Credit/Debit notes
CDN and CDNA endpoints for notes from registered suppliers
E-commerce & TCS
ECOM, ECOMA, and TCS endpoints for e-commerce operator data
Imports & SEZ
IMPG and IMPGSEZ endpoints for import-related inward supplies
Other credits
ISD and TDS endpoints for Input Service Distributor and TDS credits
Change tracking
AMDHIST endpoint for amendment history and change audit
Core invoice APIs
Retrieve B2B invoices and their amendments:| API | Table/Code | Description |
|---|---|---|
| GSTR-2A B2B | B2B | Invoices from registered suppliers (inward supplies) |
| GSTR-2A B2BA | B2BA | Amendments to B2B invoices by suppliers |
Credit/Debit note APIs
Retrieve credit and debit notes from suppliers:| API | Table/Code | Description |
|---|---|---|
| GSTR-2A CDN | CDN | Credit/Debit notes from registered suppliers |
| GSTR-2A CDNA | CDNA | Amendments to credit/debit notes |
E-commerce and TCS APIs
Retrieve e-commerce operator supplies and TCS data:| API | Table/Code | Description |
|---|---|---|
| GSTR-2A ECOM | ECOM | Supplies through e-commerce operators |
| GSTR-2A ECOMA | ECOMA | Amendments to e-commerce supplies |
| GSTR-2A TCS | TCS | Tax Collected at Source by e-commerce operators |
Import APIs
Retrieve import and SEZ-related inward supplies:| API | Table/Code | Description |
|---|---|---|
| GSTR-2A IMPG | IMPG | Imports of goods (Bill of Entry data) |
| GSTR-2A IMPGSEZ | IMPGSEZ | Imports from SEZ units/developers |
Other credit APIs
Retrieve ISD credits and TDS deductions:| API | Table/Code | Description |
|---|---|---|
| GSTR-2A ISD | ISD | Input Service Distributor credits received |
| GSTR-2A TDS | TDS | Tax Deducted at Source by deductors |
Amendment history API
Track changes to inward supplies over time:| API | Table/Code | Description |
|---|---|---|
| GSTR-2A AMDHIST | AMDHIST | Amendment history for tracking supplier changes |
Common APIs
Shared endpoints used across GSTR-2A workflow:| API | Purpose |
|---|---|
| Generate OTP | Start taxpayer authentication |
| Verify OTP | Complete authentication (6-hour session) |
| Refresh Session | Extend taxpayer session |
| Logout | End taxpayer session |
Common use cases
Use GSTR-2A APIs when you need to:- Reconcile purchase register against supplier-filed invoices visible in GSTR-2A (vendor-wise mismatch and missing invoice lists)
- Track amendments to invoices and notes using B2BA, CDNA, ECOMA, and AMDHIST for audit trails
- Monitor import and SEZ-related inward entries for period-wise ITC reconciliation (IMPG/IMPGSEZ)
- Capture ISD credits for service-heavy organizations and map them to cost centers
- Reconcile TDS/TCS credits reflected in GSTR-2A for cashflow and compliance reporting
- Build monthly inward supplies dashboards with section-wise trends and vendor compliance scores
Frequently asked questions
What is GSTR-2A and what does it contain?
What is GSTR-2A and what does it contain?
GSTR-2A is an auto-drafted inward supplies statement generated on the GST portal based on documents uploaded by suppliers in their GSTR-1 returns. GSTR-2A contains B2B invoices, credit/debit notes, import entries, ISD credits, TDS/TCS deductions, and e-commerce supplies that are relevant to Input Tax Credit (ITC) claims.
How is GSTR-2A different from GSTR-2B?
How is GSTR-2A different from GSTR-2B?
GSTR-2A is a dynamic statement that updates whenever suppliers file or amend their GSTR-1 returns, making it useful for real-time tracking. GSTR-2B is a static statement generated monthly on a GSTN schedule that provides a fixed snapshot for ITC claims. Both statements serve ITC reconciliation but GSTR-2A reflects continuous supplier activity.
Why do invoices appear or mismatch in GSTR-2A?
Why do invoices appear or mismatch in GSTR-2A?
GSTR-2A reflects invoices exactly as suppliers file them in GSTR-1. Mismatches occur when suppliers file incorrect invoice numbers, GSTINs, taxable values, or tax amounts. Missing invoices in GSTR-2A indicate that suppliers have not yet filed GSTR-1 for that period. Use the B2B endpoint to retrieve current data and compare against your purchase register.
What are the prerequisites to call GSTR-2A APIs?
What are the prerequisites to call GSTR-2A APIs?
GSTR-2A API calls require an authenticated taxpayer session. First call the Generate OTP endpoint, then verify with Verify OTP to obtain a session token valid for 6 hours. Include the session token in all subsequent GSTR-2A requests.
Which endpoints should I use for amendments?
Which endpoints should I use for amendments?
How should I handle errors and timeouts?
How should I handle errors and timeouts?
GSTR-2A API errors should be handled using standard error codes documented in the error handling guide. Common issues include session expiry (re-authenticate), rate limits (implement backoff), and GST portal downtime (retry with exponential backoff). Always validate the session before making bulk requests.
How often should I fetch GSTR-2A data?
How often should I fetch GSTR-2A data?
GSTR-2A is a dynamic statement that updates continuously as suppliers file or amend GSTR-1 returns. Fetch GSTR-2A data after the GSTR-1 filing deadline (11th of the following month) for maximum coverage, and re-fetch periodically to capture late filings and amendments. Monthly reconciliation workflows typically pull data multiple times per period.
Can I retrieve GSTR-2A data for past periods?
Can I retrieve GSTR-2A data for past periods?