PLEASE DO NOT SHARE YOUR CREDENTIALS WITH YOUR CUSTOMERSHow to Use#
The Authorization API provided by SRS is an essential step in securely authenticating users
and generating a token for accessing other SIPS services. Below is a step-by-step guide on how to use the Authorization API to obtain a bearer token.Obtain Client Credentials#
Before making a request to the Authorization API, you need to obtain yourfrom SRS's onboarding team. These credentials are unique to your account and will be used for secure access.Making a Request#
To obtain the bearer token, you need to make a POST request to the authentication URL provided by SIPS team.The request body should be in JSON format and include the following parameters:client_id: Your unique client ID provided by SRS.
client_secret: The confidential code paired with your client ID for secure access.
grant_type: Use client_credentials for machine-to-machine auth.
scope : Defines the access scope. Use ALL to request full access permissions.
Handle the Response#
After making the request, the server will respond with a 200 OK status code if the request is successful. The response will include the following data:token_type: A string indicating the type of token issued, typically 'Bearer'.
expires_in: An integer value representing the time in seconds until the token expires
(set to 24 hours).
ext_expires_in: Extended expiration time for the token (also set as 24 hours).
access_token: The bearer token that you will use to authenticate and access SRS services.
Using the Bearer Token#
The access_token obtained from the Authorization API should be included in the Authorization header of all your subsequent API requests to SRS services. This token serves as your authentication to access various SRS endpoints.Modified at 2025-09-26 10:22:47
