> 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/sahamatinet-agent-sna/integration-guide/integration-points.md).

# Integration Points

SNA defines 8 integration points, labeled A through H, corresponding to the 4 interface points: one on the AA-FIP side and one on the AA-FIU side of AA's service. Each point represents a direction of data flow that SNA monitors.

<figure><img src="https://2423266439-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCKUjTKikPLYOjZEtClEd%2Fuploads%2FnVSeKrhhl4CQ4YcjaxoY%2Fimage.png?alt=media&amp;token=2eaafd49-193a-4221-83b7-f32fef79b9cb" alt=""><figcaption></figcaption></figure>

### Integration Points Summary

| Point | Direction   | Side   | SLA        | Billing    | SaaNs      | MIS        |
| ----- | ----------- | ------ | ---------- | ---------- | ---------- | ---------- |
| A     | requestOut  | AA-FIP | ✔ Required |            | ✔ Required | ✔ Required |
| B     | responseIn  | AA-FIP | ✔ Required |            | ✔ Required | ✔ Required |
| C     | requestIn   | AA-FIP | ✔ Required |            | ✔ Required | ✔ Required |
| D     | responseOut | AA-FIP | ✔ Required |            | ✔ Required | ✔ Required |
| E     | requestOut  | AA-FIU |            | ✔ Required |            | ✔ Required |
| F     | responseIn  | AA-FIU |            | ✔ Required |            | ✔ Required |
| G     | requestIn   | AA-FIU |            | ✔ Required |            | ✔ Required |
| H     | responseOut | AA-FIU |            | ✔ Required |            | ✔ Required |

### Integration Point Details (AA-FIP Side)

<table><thead><tr><th width="145.66668701171875">Point</th><th width="124">Direction</th><th>What to Capture</th></tr></thead><tbody><tr><td>A) requestOut</td><td>AA → FIP</td><td>Capture outgoing request data: API type, timestamp, target FIP ID, request size</td></tr><tr><td>B) responseIn</td><td>FIP → AA</td><td>Capture incoming response data: HTTP status code, response time (ms), response body size</td></tr><tr><td>C) requestIn</td><td>FIP → AA</td><td>Capture incoming FIP notifications: API type, timestamp, source FIP ID</td></tr><tr><td>D) responseOut</td><td>AA → FIP</td><td>Capture outgoing response data: HTTP status code, timestamp</td></tr></tbody></table>

### Integration Point Details (AA-FIU Side)

| Point          | Direction | Applicable APIs                                                                                              | What to Capture                                           |
| -------------- | --------- | ------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------- |
| E) requestOut  | AA → FIU  | /Consent/Notification, /FI/Notification, /Heartbeat                                                          | Outgoing request data: API type, timestamp, target FIU ID |
| F) responseIn  | FIU → AA  | Responses to the APIs at point E                                                                             | Incoming response data: HTTP status code, timestamp       |
| G) requestIn   | FIU → AA  | /Consent, /Consent/handle, /Consent/fetch, /FI/request, /FI/fetch, /Consent/Notification¹, /FI/Notification¹ | Incoming request data: API type, timestamp, source FIU ID |
| H) responseOut | AA → FIU  | Responses to the APIs at point G                                                                             | Outgoing response data: HTTP status code, timestamp       |

> ¹ ReBIT specifications allow these notifications to be sent to the AA by an FIU. Capture them only if your AA supports receiving them

📌 Some APIs also require additional attributes (`addlAttr`) on both the AA-FIP and AA-FIU interfaces


---

# 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/sahamatinet-agent-sna/integration-guide/integration-points.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.