A Consolidated Account Statement is the widest snapshot an Indian investor can get: every mutual-fund folio from CAMS and KFintech, every demat holding from NSDL and CDSL. Grappi splits it into the three things that actually happen. /v1/cas/request places the statement request with the RTA, returning the CAPTCHA the investor answers. /v1/cas/read finds the resulting mail over IMAP, decrypts the PDF and parses it into holdings and transactions. /v1/cas/import folds that into a portfolio keyed on ISIN, so next month's statement updates positions instead of duplicating them, with cost, gain and XIRR rolled up. Live use is switched on after a business check.
- APIs
- 7 you can call
- Consent
- Bound to every read
- Audit
- Every call in a hash-chained log
APIs in CAS Portfolio Fetch
Every API shares the same key, error format and audit log. Each one is switched on for your account separately.
CAS provider matrix
Which RTAs can be requested server-side today (KFintech yes; NSDL/CDSL need an investor OTP, so use the mailbox scan instead).
GET /v1/cas/request/providersReference3.1 CAS Auto Request — open session
Opens a session with the RTA and returns the CAPTCHA image the investor must read.
POST /v1/cas/request/sessionReference3.1 CAS Auto Request — submit
Submits the statement request with the CAPTCHA answer. The RTA then e-mails the password-protected CAS to the investor.
POST /v1/cas/request/submitReference3.1 CAS Auto Request — one call
Opens the RTA session, completes its verification step and submits, retrying with a fresh session on a misread. One call, one price regardless of attempts.
POST /v1/cas/request/autoReference3.2 CAS Auto Read — mailbox scan
Finds the RTA's mail over IMAP, pulls the attachment, decrypts and parses it. Use an app password.
POST /v1/cas/read/mailbox/scanReference3.3 CAS Auto Import — import parsed CAS
Folds a parsed CAS into the portfolio: one stable key per position (so next month updates rather than duplicates), cost/value/gain rolled up, XIRR when available.
POST /v1/cas/import/documentReference3.3 CAS Auto Import — current portfolio
The latest imported CAS portfolio for this tenant.
GET /v1/cas/portfolioReference
How you get CAS Portfolio Fetch
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/cas/request/submit 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 3.1 cas auto request — submit
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 CAS Portfolio Fetch call takes minutes, not days.
Integration guide
The quickstart covers keys, auth, idempotency, the error envelope, and paise money units. The catalog documents every CAS Portfolio Fetch 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 CAS Portfolio Fetch API into my app. Endpoints: - GET /v1/cas/request/providers (CAS provider matrix) - POST /v1/cas/request/session (3.1 CAS Auto Request — open session) - POST /v1/cas/request/submit (3.1 CAS Auto Request — submit) - POST /v1/cas/request/auto (3.1 CAS Auto Request — one call) - POST /v1/cas/read/mailbox/scan (3.2 CAS Auto Read — mailbox scan) - POST /v1/cas/import/document (3.3 CAS Auto Import — import parsed CAS) - GET /v1/cas/portfolio (3.3 CAS Auto Import — current portfolio) 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.