Bond reference data and live G-Secs.

Bonds

Look up issuer, coupon, maturity, and rating for any bond by ISIN, and read the government securities list with coupon and yield to maturity. Both endpoints are reference data and free to call.

OpenSelf-serve. Grantable on any key, no access request.
2
endpoints in this rail
Open
access tier
Consent
bound on every read
Audit
hash-chained trail

Endpoints

Every endpoint shares auth, idempotency, consent and metering hooks, a unified error envelope, and a hash-chained audit trail.

GET
Bond reference
/v1/bonds/reference

Issuer, coupon, maturity, rating by ISIN.

GET
G-Secs + yields
/v1/bonds/gsec

Government securities with coupon + YTM.

How it works

From signup to a live Bonds call in four steps.

1

Create a free account

Sign up and get a prefunded sandbox key in seconds. No card required.

2

Unlock the rail

Grant the scope to any key yourself. No access request, no business verification.

3

Make your first call

Send the sample request to /v1/bonds/reference with your sandbox key and read back live JSON.

4

Go live

Swap the sandbox key for a live key. Every call is metered, itemized, and audit-chained.

Call bond reference

The flagship call for this rail. Swap the sandbox key for your own and you are live.

get-bonds-reference.sh
curl https://api.grappi.in/v1/bonds/reference?isin=INE040A08328 \
-H "x-api-key: sk_sandbox_••••"

Developer ready

Docs, MCP, and a prompt that does the work

Every rail ships with an integration guide, an MCP server for AI agents, and a ready-to-paste prompt, so your first Bonds call takes minutes, not days.

Integration guide

The quickstart covers keys, auth, idempotency, the error envelope, and paise money units. The catalog documents every Bonds 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://api.grappi.in",
        "GRAPPI_API_KEY": "sk_sandbox_••••"
      }
    }
  }
}

Prompt-ready integration

Paste this into Claude, Cursor, or any coding agent. It carries the real contract rules, so the generated client matches the gateway on the first try.

integrate-bonds.prompt
Integrate the Grappi Bonds API into my app.

Endpoints:
- GET /v1/bonds/reference (Bond reference)
- GET /v1/bonds/gsec (G-Secs + yields)

Contract rules: send the key as the x-api-key header, treat all money as integer paise (₹1.00 = 100), send an Idempotency-Key on every POST, and branch on the error envelope error.code (handle 402 insufficient_balance, 403 consent_required, 422 validation_failed, 429 rate_limited).

Write a small typed client for these endpoints plus one worked call, with validation and error handling, in my project's language.

Frequently asked questions

Can I try it for free?

Yes. Signing up creates a sandbox key, so you can call this rail immediately without a card. Sandbox calls run against test data, not production.

What comes with every endpoint?

Auth, idempotency, consent and metering hooks, a unified error envelope, and a hash-chained audit trail — identical across every rail on the platform.

What do I need to go live?

Self-serve. Grantable on any key, no access request. Once live, the same key and the same contract carry over from sandbox.

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 regulated rails stay locked until an access request is approved.

Get started

Start building with Bonds

Create a free sandbox account, get a prefunded key, and call Bonds on the same contract as every other rail.

  • Instant sandbox key, no card required
  • One key works across every rail
  • Open rails are live the moment you sign up
Consent-bound on every read. DPDP and RBI-AA aligned.