> 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/onboarding-to-saans/faq-saans.md).

# FAQ SaaNs

Frequently asked questions on Saans, Sahamati’s FIP API health monitoring service, covering onboarding, data publishing, signals, data access and rate limits.

**Q: What is Saans, and why is it important?**\
Saans (Swasthya of AA Network as a Service) is Sahamati's dashboard for FIP API health in real-time, built from metrics reported by AAs. Kindly refer [Onboarding to Saans | SahamatiNet](https://developer.sahamati.org.in/onboarding-to-saans) for more information.

**Q: How does Saans data collection work?**\
Each AA summarises request/response signals over 10-minute windows into percentiles and pushes them to Sahamati, which aggregates across all AAs.

**Q: Which FIP APIs does Saans monitor?**\
Consent Post, FI Request, FI Fetch, Account Discovery, Account Linking, Confirm Linking, and Delinking.

**Q: What is the Saans onboarding process?**\
Expose a public endpoint, whitelist 20.204.209.246 and 13.71.48.89, validate JWTs with Sahamati's certificate, and submit the onboarding form to <memberservices@sahamati.org.in>. Notifications start T+1.

**Q: What data should AAs publish to Saans?**\
Synchronous API metrics (discovery, linking, FI request) per FIP and asynchronous FI notification metrics, each every 10 minutes.

**Q: What are signals and events in Saans?**\
A signal aggregates all events for one FIP in a 10-minute window. If there were no events, skip the signal.

**Q: How can I access aggregated health data from Saans?**\
Through the SAANS API (see How to access the SAANS API on the developer portal); your registered endpoint also receives FIP health notifications.

**Q: Does Saans share individual FIP data across AAs?**\
No. Signals from all AAs are pooled and cannot be filtered by AA.

**Q: Does Saans collect transaction counts or transaction details?**\
No. Saans collects only summarised health metrics, never counts or individual transactions.

**Q: Is there any rate limit on the Saans API that AAs use to publish data?**\
Yes, 300 requests per 24 hours; beyond that, the API returns HTTP 429.


---

# 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/onboarding-to-saans/faq-saans.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.