Endpoints & Authentication
Last updated
Was this helpful?
SNA pushes 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.
Production
https://api.sahamati.org.in/sla-inputs/aa/v1/push
UAT
https://api.uat.sahamati.org.in/sla-inputs/aa/v1/push
The SLA push endpoint uses token-based authentication. The authentication token will be generated by SNA and stored securely. As part of the SNA deployments the admin will have to configure the entityId and the secret as a Kubernetes secret file for the SNA to generate the token. SNA handles the token injection into request headers automatically.
📌 Authentication credentials are issued per AA by Sahamati. Tokens must be stored securely in your cluster and must not be committed to version control.
Last updated
Was this helpful?
Was this helpful?