1
Initiate the UI to access the user token and org id
Our Billing SDK expects the user token and org id to be passed to it. This is used to validate the user session and the organization session.
We are in progress of adding support of org id. We will update this section once we have added support of org id.
2
Setup an authentication endpoint in your application
Our Billing API requires an authentication endpoint in your application that will be used to validate the user session.For more information on how the authentication works, please refer to the Authentication and Authorization section.
This endpoint should be a private endpoint which can accept the user session token of your application and validate it, and then return the user information.Expected Request Headers:Expected Response if user is authenticated and belong to the organization:Expected Response if user is not authenticated or does not belong to the organization:
Http status code: 401This ensures that the user information is validated and the user is authenticated by your service.