Pull a taxpayer's filed income-tax returns with their own income-tax portal login, and verify ITR-V filings for up to the last five years. The password is passed straight through: never stored, never logged.
- APIs
- 2 you can call
- Consent
- Bound to every read
- Audit
- Every call in a hash-chained log
APIs in Income verification (ITR)
Every API shares the same key, error format and audit log. Each one is switched on for your account separately.
ITR fetch
Filed income-tax returns pulled with the taxpayer's own income-tax portal login. The password is passed through, never stored or logged.
POST /v1/tax/itr/fetchReferenceITR-V verification
Checks filed returns for the last 1 to 5 years (years, default 3) with the taxpayer's password or a session_id.
POST /v1/tax/itr/verifyReference
What teams use it for
Use cases for each Income verification (ITR) check. See how they combine with other products on the use cases page.
Filed returns pulled with the taxpayer’s own income tax portal login.
- Verify self-employed and business income for loans.
- Replace uploaded return PDFs with data from the tax portal itself.
- Support higher insurance cover with declared income.
Checks the returns filed for the last one to five years.
- Confirm that returns a customer uploaded were really filed.
- Check filing history before lending.
How you get Income verification (ITR)
From a new account to a live call in four steps.
Create your account
Sign up with your work email and create an app and its key. No API is active on a new account.
Pay and subscribe
Add money to your wallet, then subscribe to this API in Dashboard → API access. We switch it on for your account after your payment.
Make your first call
Once the API is activated, send the sample request to /v1/tax/itr/fetch with your key and read back the JSON.
Go live
Use a live key in production. Every call is checked against the APIs activated for you, drawn from your prepaid wallet, and recorded in a hash-chained audit trail.
Call itr fetch
The main call for this product. Use your own key once this API is switched on for your account.
Developer ready
Docs, MCP, and a prompt that does the work
Every product ships with an integration guide, an MCP server for AI agents, and a ready-to-paste prompt, so your first Income verification (ITR) call takes minutes, not days.
Integration guide
The quickstart covers keys, auth, idempotency, the error envelope, and paise money units. The catalog documents every Income verification (ITR) endpoint with a live sample you can run from the playground.
MCP server for AI agents
grappi-mcp exposes the API as agent tools over the same gateway, so every tool call keeps auth, consent, metering, and audit. Drop this into your MCP client config.
{
"mcpServers": {
"grappi": {
"command": "npx",
"args": ["grappi-mcp"],
"env": {
"GRAPPI_API_BASE": "https://grappi.ai",
"GRAPPI_API_KEY": "your-api-key"
}
}
}
}Prompt-ready integration
Paste this into your coding assistant or agent. It carries the real contract rules, so the generated client matches the gateway on the first try.
Integrate the Grappi Income verification (ITR) API into my app. Endpoints: - POST /v1/tax/itr/fetch (ITR fetch) - POST /v1/tax/itr/verify (ITR-V verification) Contract rules: send the key as a Bearer token in the Authorization header, treat all money as integer paise (100 paise is one rupee), send an Idempotency-Key on every POST, and branch on the error envelope error.code (handle 402 insufficient_balance, 403 api_not_activated, 403 consent_required, 422 validation_failed, 429 rate_limited, 503 api_unavailable). Write a small typed client for these endpoints plus one worked call, with validation and error handling, in my project's language.
Questions
How do I start?
Create an account and add money to your wallet. Then subscribe to this API in your dashboard and we switch it on for your account.
What comes with every API?
Auth, idempotency, consent and metering hooks, a unified error envelope, and a hash-chained audit trail, identical across every API on the platform.
What do I need to go live?
Subscribe to the API in your dashboard and we switch it on for your account after your payment. The request and reply format is the same in test and in production.
Is this compliant for regulated use?
Reads are consent-bound and DPDP and RBI-AA aligned. Every call lands in a hash-chained audit trail, and every API is switched on for your account individually.