> For the complete documentation index, see [llms.txt](https://developer.sahamati.org.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.sahamati.org.in/central-registry/faq-central-registry.md).

# FAQ Central Registry

Frequently asked questions on the Sahamati Central Registry, covering listing requirements, entity metadata, access control, API endpoints and rate limits.

**Q: What is the Central Registry and why is it important?**\
The Central Registry is a central repository that maintains accurate, verifiable metadata (e.g., identifiers, API endpoints, IP addresses, public cryptographic keys, etc.) of onboarded AAs, FIPs, and FIUs for automated discoverability and trusted communication among such entities.

**Q: What entities can be listed in the Central Registry?**\
Regulated Entities like Account Aggregators (AAs), Financial Information Providers (FIPs), and Financial Information Users (FIUs).

**Q: What are the key metadata attributes required for listing in the Central Registry?**\
Entity ID, Legal name, Entity type, Base URL (format `v1:<url>`, `v2:<url>`), public key in JWK format, and inbound/outbound IPs, to name a few. For the complete attributes list, kindly refer <https://developer.sahamati.org.in/central-registry/json-template>

**Q: How should I choose my Entity ID?**\
Follow the Entity ID Naming Convention published by the Sahamati Member Success function, which can be found in this FAQ <https://membersuccess.sahamati.org.in/member-services/cr-onboarding-guide/faqs>

**Q: How do I generate the public key/certificate for listing?**\
Create an RSA key pair in JWK format (kty=RSA, use=sig, alg=RS256, unique kid) as per the How To Generate a Certificate guide. Never share the private key.

**Q: How do I get listed in the Central Registry (CR)?**\
Kindly refer to the CR Onboarding Guide at [https://membersuccess.sahamati.org.in/member-services/cr-onboarding-guide](https://membersuccess.sahamati.org.in/member-services/cr-onboarding-guide/faqs)

**Q: How does role-based access control (RBAC) work in the Central Registry?**\
AAs can retrieve metadata information of FIPs and FIUs **but not** of other AAs, while FIPs and FIUs can retrieve metadata information about AAs **but not** of other FIUs and FIPs.

**Q: What are the Central Registry API endpoints?**\
`GET /cr/v2/entityInfo/{type}` for all entities of a type, `GET /cr/v2/entityInfo/{type}/{id}` for an entity of a specific type with entityID

**Q: Can I still use the Central Registry V1 APIs?**\
No. V1 APIs were decommissioned in October 2024 and would return an HTTP response status of 410; Instead use the /cr/v2 endpoints.

**Q: What security measures protect Central Registry data?**\
HTTPS with TLS 1.2+, bearer-token authentication, role-based access control, and database encryption at rest.

**Q: Can I update my Central Registry information directly?**\
Not via API yet. Send change requests for your Central Registry details to <memberservices@sahamati.org.in>. Kindly refer [Checklists and JSON - Templates | Sahamati](https://membersuccess.sahamati.org.in/member-services/cr-onboarding-guide/checklists-and-json-templates) for more information.

**Q: Is there any rate limit enforced on the Central Registry GET APIs?**\
Yes, 1000 requests per 24 hours; when requests exceed this rate limit, the API returns *HTTP 429 Too Many Requests.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.sahamati.org.in/central-registry/faq-central-registry.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.