> 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/sla/api-reference/sla-notification-payload.md).

# SLA Notification Payload

SNA also pushes a Notification metrics payload to the Sahamati endpoint every 10 minutes. This payload captures incoming notification traffic from FIPs to the AA, including notification counts and FI notification status breakdowns. The tag for this payload is not-fipMetrics-aa.

### Schema Reference

<table><thead><tr><th width="166">Field</th><th width="141.666748046875">Type</th><th>Description</th></tr></thead><tbody><tr><td>agentVersion</td><td>string</td><td>Version of the SNA agent generating this payload</td></tr><tr><td>jsonVersion</td><td>string</td><td>Version of the JSON schema (e.g. "1.0.0")</td></tr><tr><td>tag</td><td>string</td><td>"not-fipMetrics-aa" identifies this as a notification-metrics payload from AA perspective of FIP</td></tr><tr><td>txnId</td><td>string</td><td>Unique transaction ID for this push request</td></tr><tr><td>fromDateTime</td><td>string</td><td>Start of the 10-minute reporting window (ISO 8601, UTC)</td></tr><tr><td>toDateTime</td><td>string</td><td>End of the 10-minute reporting window (ISO 8601, UTC)</td></tr><tr><td>duration</td><td>int</td><td>Duration in seconds of the reporting window (600 for 10 minutes)</td></tr><tr><td>aaId</td><td>string</td><td>Entity ID of the Account Aggregator</td></tr><tr><td>fips[].fipId</td><td>string</td><td>Entity ID of the FIP for which notification metrics are reported</td></tr><tr><td>fips[].metrics[].type</td><td>string</td><td>Metric type code: finot, alnot, or cnot</td></tr><tr><td>fips[].metrics[].counts</td><td>array[int]</td><td>Count values aligned to countFields enum in the notification payload</td></tr><tr><td>fips[].metrics[].status</td><td>array[int]</td><td>Status values (only for type "finot"): [succRecdCnt, failRecdCnt, readyRecdCnt, deniedRecdCnt, deliveredRecdCnt, timeoutRecdCnt, intermediateRecdCnt]</td></tr></tbody></table>

### Notification Metric Types

<table><thead><tr><th width="89.66668701171875">Code</th><th>Full Name</th><th>Description</th></tr></thead><tbody><tr><td>finot</td><td>fiNotificationRecd_finot</td><td>FI notifications received from FIP counts and status breakdown (READY, DELIVERED, DENIED, TIMEOUT, PENDING)</td></tr><tr><td>alnot</td><td>accountLinkNotificationRecd_alnot</td><td>Account link notifications received from FIP</td></tr><tr><td>cnot</td><td>consentNotificationRecd_cnot</td><td>Consent notifications received from FIP</td></tr></tbody></table>

### Notification Count Fields

The counts array is positionally aligned to these fields:

<table><thead><tr><th width="101.6666259765625">Position</th><th width="264.666748046875">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>totalRecdCnt</td><td>Total notifications received. For FI notifications: count only the last /FI/Notification where all FIStatus states are terminal (READY, DELIVERED, DENIED, TIMEOUT).</td></tr><tr><td>2</td><td>200OKSentCnt</td><td>HTTP 200 OK responses sent back</td></tr><tr><td>3</td><td>400BadReqSentCnt</td><td>HTTP 400 Bad Request responses sent</td></tr><tr><td>4</td><td>401UnauthorizedReqSentCnt</td><td>HTTP 401 Unauthorized responses sent</td></tr><tr><td>5</td><td>403ForbiddenReqSentCnt</td><td>HTTP 403 Forbidden responses sent</td></tr><tr><td>6</td><td>404NotFoundSentCnt</td><td>HTTP 404 Not Found responses sent</td></tr><tr><td>7</td><td>409IdempotencyErrorReqSentCnt</td><td>HTTP 409 Idempotency Error responses sent</td></tr><tr><td>8</td><td>412PreConditionFailedSentCnt</td><td>HTTP 412 Precondition Failed responses sent</td></tr><tr><td>9</td><td>429TooManyReqsSentCnt</td><td>HTTP 429 Too Many Requests responses sent</td></tr><tr><td>10</td><td>4xxOtherErrorsSentCnt</td><td>All other 4xx error responses sent</td></tr><tr><td>11</td><td>500InternalServerErrorSentCnt</td><td>HTTP 500 Internal Server Error responses sent</td></tr><tr><td>12</td><td>502BadGatewaySentCnt</td><td>HTTP 502 Bad Gateway responses sent</td></tr><tr><td>13</td><td>503ServiceUnavailableSentCnt</td><td>HTTP 503 Service Unavailable responses sent</td></tr><tr><td>14</td><td>504GatewayTimeoutSentCnt</td><td>HTTP 504 Gateway Timeout responses sent</td></tr><tr><td>15</td><td>5xxOtherErrorsSentCnt</td><td>All other 5xx error responses sent</td></tr></tbody></table>

### FI Notification Status Fields

The status array is only present for the "finot" metric type and is positionally aligned to these fields:

| Position | Field Name          | Description                                                                                                      |
| -------- | ------------------- | ---------------------------------------------------------------------------------------------------------------- |
| 1        | succRecdCnt         | Notifications with at least one READY or DELIVERED state in final /FI/Notification                               |
| 2        | failRecdCnt         | Notifications where all accounts are DENIED or TIMEOUT (none READY or DELIVERED) does not include 4xx/5xx errors |
| 3        | readyRecdCnt        | Notifications with terminal state READY in final /FI/Notification                                                |
| 4        | deniedRecdCnt       | Notifications with terminal state DENIED in final /FI/Notification                                               |
| 5        | deliveredRecdCnt    | Notifications with terminal state DELIVERED in final /FI/Notification                                            |
| 6        | timeoutRecdCnt      | Notifications with terminal state TIMEOUT in final /FI/Notification                                              |
| 7        | intermediateRecdCnt | Notifications still in non-terminal state PENDING                                                                |

> 📌 Time difference between FIReq 200 OK and failure notification (Note: All accounts are marked as DENIED or TIMEOUT in the final /FI/Notification, i.e., none of the states are READY.)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.sahamati.org.in/sahamatinet-agent-sna/sla/api-reference/sla-notification-payload.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.