SRS Integration Partner Services
HomeV1 APIsV2 APIs
HomeV1 APIsV2 APIs
  1. SRS API Guides
  • SRS Integration Partner Services (SIPS)
  • Getting Started
    • Introduction
    • Web Hooks
    • FAQs
  • SRS API Guides
    • Authentication
    • Reference Data
    • Product Data
    • Invoices
    • Orders
    • Order Details
  1. SRS API Guides

Authentication

warning-icon.png
PLEASE DO NOT SHARE YOUR CREDENTIALS WITH YOUR CUSTOMERS

Authentication for SIPS API#

To interact with the SRS Integration Partner Services (SIPS) API, you need to authenticate your requests using a bearer token. This section explains the required credentials, how to obtain them, and how to use the bearer token.

Required Credentials#

To access the SIPS API, you need the following credentials:
client_id: A unique code given to you by SRS to identify your account.
client_secret: A confidential code provided by SRS, 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.
key-icon.png To obtain these credentials, please contact APISupportTeam@srsdistribution.com

Obtaining the Bearer Token#

The bearer token is generated using the /Authentication/token endpoint endpoint. This token must be included in the header of all subsequent API requests to authenticate your access.
Steps to Obtain the Bearer Token:
1.
Send a POST request to the /Authentication/token endpoint with your client_id, client_secret, grant_type and scope.
2.
Receive a response containing the access_token, which you will use for authentication.
Example Request:

Using the Bearer Token#

Once you have obtained the bearer token, include it in the Authorization header of your API requests. The token is valid for 1 hour and needs to be refreshed periodically.
Example Authorization Header:
By following these steps, you can securely authenticate and interact with the SIPS API to access the services provided by SRS.
Modified at 2025-09-26 10:20:11
Previous
FAQs
Next
Reference Data
Built with