Consolidated portfolio

Every broker and every folio in one portfolio.

GET /v1/portfolio fans out across every broker connection on the key, whatever the provider, folds in the mutual funds from the imported CAS, and returns one portfolio deduplicated by ISIN. The same stock held at three brokers is one position with a per-broker breakdown, not three rows. Allocation, concentration and a 0-100 score come back in the same call, and a broker whose daily token expired is reported as a failed source rather than quietly dropped from the totals.

APIs
4 you can call
Consent
Bound to every read
Audit
Every call in a hash-chained log

APIs in Consolidated portfolio

Every API shares the same key, error format and audit log. Each one is switched on for your account separately.

  • Consolidated portfolio

    Every linked broker plus the imported CAS in one view: holdings deduplicated by ISIN, totals, P&L, allocation, concentration and score. One call, whatever the brokers.

    GET /v1/portfolioReference
  • Deduplicated holdings

    The same stock held at three brokers comes back as ONE position, with a per-broker contributions breakdown. Filter to equity, mutual funds, ETFs or bonds.

    GET /v1/portfolio/holdingsReference
  • Allocation + concentration

    Weights by asset class and by broker, plus the concentration a plain P&L screen hides: largest holding, top-5 weight, HHI and effective holdings.

    GET /v1/portfolio/allocationReference
  • Portfolio score

    A 0-100 structural health score that always ships its own reasons: breadth, concentration, asset mix and standing, each with its weight and a plain-language note.

    GET /v1/portfolio/scoreReference

How you get Consolidated portfolio

From a new account to a live call in four steps.

  1. Create your account

    Sign up with your work email and create an app and its key. No API is active on a new account.

  2. 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.

  3. Make your first call

    Once the API is activated, send the sample request to /v1/portfolio with your key and read back the JSON.

  4. 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 consolidated portfolio

The main call for this product. Use your own key once this API is switched on for your account.

GET /v1/portfolio
curl https://grappi.ai/v1/portfolio? \
-H "Authorization: Bearer $GRAPPI_API_KEY"

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 Consolidated portfolio call takes minutes, not days.

Integration guide

The quickstart covers keys, auth, idempotency, the error envelope, and paise money units. The catalog documents every Consolidated portfolio 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.

mcp.json
{
  "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-consolidated-portfolio.prompt
Integrate the Grappi Consolidated portfolio API into my app.

Endpoints:
- GET /v1/portfolio (Consolidated portfolio)
- GET /v1/portfolio/holdings (Deduplicated holdings)
- GET /v1/portfolio/allocation (Allocation + concentration)
- GET /v1/portfolio/score (Portfolio score)

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.