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
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
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.
Last updated
Was this helpful?