> 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/frequently-asked-questions.md). # Frequently Asked Questions This FAQ section summarises the key technical aspects of the Sahamati Services. ## Sahamati Service-Specific FAQs

		Cover image
FAQ Central Registry	Frequently asked questions on the Sahamati Central Registry, covering listing requirements, entity metadata, access control, API endpoints and rate limits.	Central Registry@1x.png
FAQ Token Service	Frequently asked questions on Sahamati’s Token Service, covering token types, token generation, rate limits, error responses and Entity Secret rotation.	Token Service@1x.png

		Cover image
FAQ SaaNs	Frequently asked questions on Saans, Sahamati’s FIP API health monitoring service, covering onboarding, data publishing, signals, data access and rate limits.	SaaNs@1x.png
FAQ SNA	Frequently asked questions on the SahamatiNet Agent (SNA), covering deployment, data sharing, resource requirements, troubleshooting, logs and error handling.	SNA (SahamatiNet Agent)@1x.png

## General **Q: Where can I monitor the status of various Sahamati applications?**\ Live status is available at . ## Environments and Testing **Q: What are the base URLs for each environment?**\ Token Service: api.sandbox.sahamati.org.in, api.uat.sahamati.org.in, api.sahamati.org.in. Central Registry: api.sandbox.sahamati.org.in/cr, uatcr.sahamati.org.in, cr.sahamati.org.in. **Q: How can I onboard an entity in the UAT environment?**\ Through the AA Commons self-service portal at . ## Integration Steps & Best Practices **Q: What is the recommended integration sequence?** * Generate User Token * Reset Secret * Read Secret * Generate Entity Token * Fetch CR metadata * Test ReBIT API flows * Certify * Get CR listing * Then go live **Q: Can I move directly from UAT to Production?**\ No. Movement to Production does not happen directly from UAT; Production has its own onboarding process. Kindly refer [Getting Started with Sahamati | Sahamati](https://membersuccess.sahamati.org.in/) for more information. **Q: What are the environment endpoints?** * Sandbox: api.sandbox.sahamati.org.in/iam, api.sandbox.sahamati.org.in/cr * UAT: api.uat.sahamati.org.in/iam and api.uat.sahamati.org.in/cr **Q: What data should I use in UAT vs production?**\ UAT must use only dummy data, with no PII or real or replica accounts. Real customer data belongs only in Production. **Q: How should I handle API errors?**\ Handle each HTTP status, log error bodies with the txnId, and retry with exponential backoff. **Q: What support is available during integration?**\ Kindly write to for onboarding and technical queries. ## Key Contacts & Resources **Member Services** (Central Registry *- Onboarding/Offboarding* and Token Service, Technical queries, SPOC changes, Secret Rotation, Saans)**:** **Developer portal:** **Self Service Portal:** **API status:** --- # 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/frequently-asked-questions.md?ask=&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.