Product
MCP ManagementHosted servers, scoped access, call logsAPI CatalogDiscover, organize, and score your APIsAPI TestingInspect quality and try your MCP toolsAPI ContractsChoose what each audience can access
How it worksPricingBlogDocsAbout SutraStart free
Sutra / WATCH

WATCH · Account Aggregator

Account Aggregator spec changes,
tracked for you.

Consent artefacts and the FI data fetch flow, per ReBIT and Sahamati. What changed, when, and which circular caused it — free, no account.

Current version
2026.09
Authority
Sahamati / ReBIT
Last reviewed
2026-09-20
Endpoints tracked
7

No change recorded since Sutra began tracking Account Aggregator on 24 Sep 2026. When one lands, it appears here field by field, with the circular behind it.

Changes

Nothing yet. This page is the record: every change from here on is kept, with its diff.

What Sutra tracks for Account Aggregator

MethodPathWhat it does
POST/ConsentRaise a consent request
GET/Consent/handle/{consentHandle}Check whether the customer has answered
POST/Consent/revokeRevoke a consent
GET/Consent/{consentId}Fetch the signed consent artefact
GET/FI/fetch/{sessionId}Fetch the gathered data
POST/FI/requestRequest financial information
POST/Notification/FIReceive a data-ready notification

Sources Sutra polls

Sahamati ecosystem participants — Who is live, testing or still building on the AA network.

Checked 17 Nov 2026 · 2 change(s) recorded. source.

Sahamati specifications index — The ReBIT specification index for the AA ecosystem.

Checked 17 Nov 2026 · 7 change(s) recorded. source.

This is Sutra's transcription of ReBIT AA Technical Specification, not the specification itself, and it has not yet been checked line by line against the authority's own copy. Read the source: Sahamati / ReBIT. Changes are announced at sahamati.org.in/account-aggregator-technical-specifications/.