> 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/billing/api-reference/endpoints-and-authentication.md).

# Endpoints & Authentication

SNA pushes billing data to a Sahamati-hosted HTTPS endpoint. Sahamati provides two variants of this endpoint, one for UAT (for testing your integration) and one for Production.

#### Billing Push Endpoints

| Environment | Endpoint URL                                               |
| ----------- | ---------------------------------------------------------- |
| Production  | <https://data.sahamati.org.in/metrics/billing/v1/push>     |
| UAT         | <https://data.uat.sahamati.org.in/metrics/billing/v1/push> |

Method: `POST`

#### Request Headers

| Header         | Required | Description                     |
| -------------- | -------- | ------------------------------- |
| `x-api-key`    | Yes      | Authentication token for the AA |
| `Content-Type` | Yes      | `application/json`              |

#### Authentication

The billing push endpoint uses token-based authentication. SNA generates the authentication token using the entityId and secret configured during deployment, and adds it to the `x-api-key` header automatically.

The `aaId` in the payload must match the AA identified by the token. Otherwise, the request is rejected.

#### IP Whitelisting

Requests are accepted only from IP addresses whitelisted for the AA. Share the outbound IP addresses of your SNA deployment with Sahamati before testing in UAT and before going live in Production. Requests from other IP addresses are rejected with HTTP 403.

> 📌 Authentication credentials are issued per AA by Sahamati. They must be stored securely and must not be committed to version control.


---

# 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/billing/api-reference/endpoints-and-authentication.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.