Pull a consumer's credit bureau report by PAN, name, date of birth, mobile and pincode, with the bureau score, account list and enquiry history. The call needs the consumer's recorded consent: that they agreed, when, and the IP they agreed from. Every pull fires a consumer alert.
- APIs
- 1 you can call, 1 more on request
- Consent
- Bound to every read
- Audit
- Every call in a hash-chained log
APIs in Credit Bureau
Every API shares the same key, error format and audit log. Each one is switched on for your account separately.
Credit bureau report
Credit bureau report by PAN, name, date of birth, mobile and pincode. The consumer's consent is required (given, timestamp, the IP they consented from); every pull is audited and fires a consumer alert.
POST /v1/credit/bureau-reportReference
Available on request
We set these checks up for your account. Subscribe to the one you need and we will have it ready for you.
- On requestSubscribe
Credit history lookup
Reads a summary of a person's credit history as part of an identity check.
What teams use it for
Use cases for each Credit Bureau check. See how they combine with other products on the use cases page.
The consumer’s credit report, pulled with their recorded consent.
- Assess repayment history and existing loans before lending.
- Set limits for cards, credit lines and pay-later products.
- Review credit before leasing and rental decisions.
Credit history lookup
On requestA summary of a person’s credit history as part of an identity check.
- Add a quick credit summary to identity checks.
- Pre-screen applicants before pulling a full report.
How you get Credit Bureau
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/credit/bureau-report 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 credit bureau report
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 Credit Bureau call takes minutes, not days.
Integration guide
The quickstart covers keys, auth, idempotency, the error envelope, and paise money units. The catalog documents every Credit Bureau 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 Credit Bureau API into my app. Endpoints: - POST /v1/credit/bureau-report (Credit bureau report) 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.