Postman configuration for authorizing Site24x7 requests
For configuring Postman to use OAuth 2.0 authorizations, you will need a Client ID and Client Secret of a web-based client. If you already have one, you can skip Part I and directly move to Part II; else follow the steps below:
Provide a name for the client and select the Type as Web based. Fill in the rest of the form and click Create. For example, the Homepage URL can be https://www.site24x7.com/ and the Authorized Redirect URI can be https://www.site24x7.com/app/OAuth2CallBack
The Client ID and Client Secret will be generated for the respective client. This is mandatory for completing the configuration.
Note: Do not disclose the Client ID and Client Secret to anyone.
Part II: Configuring Postman
Once the Client ID and Client Secret are generated, please follow the steps below:
Open Postman and create a new request.
Go to Authorization (besides Params). Choose OAuth 2.0 as the Type from the drop-down. Note: Ensure the authorization data is added to Request Headers and not Request URL. You can change this from the corresponding drop-down.
If you have an access_token, you can use it to authorize your requests. Fill in the text box provided for Access Token as https://accounts.zoho.com/oauth/v2/token. You can now send your requests with Postman with this OAuth configuration.
If you do not have an access_token yet, follow the steps below:
Click on the Get New Access Token (beneath the text box provided for filling the access_token). Fill in the name for the token, the Client ID and Client Secret generated in the previous steps. Click on Request Token. Note: The callback URL should be among the Authorized Redirect URL of the corresponding web-based client. The scopes vary with the API being called (for example: Site24x7.Admin.Create, Site24x7.Admin.Read etc.) Callback URL: https://www.site24x7.com/app/OAuth2CallBack Auth URL: https://accounts.zoho.com/oauth/v2/auth Access Token URL: https://accounts.zoho.com/oauth/v2/token
Click on Accept for authorizing access to the information asked.
Note: In case you get the error ERROR_invalid_redirect_uri, check if the given Callback URL is atleast one among the Authorized Redirect URIs given during the creation of the web-based client type (Refer Part I).
Click on Use Token to start using the token.
Sample GET request with the above configuration. Click Send to authorize your request with the new access token.