Product Version: 6.5.0.0
Overview
This article provides step-by-step instructions on how to access and use the Saner CVEM API for both on-premise and cloud environments. The API enables seamless integration with external tools for automation, reporting, and management tasks.
Step 1: Select the POST Option
Open your preferred API client such as Postman, cURL, or any equivalent tool.
Choose the POST method for your API request.
Step 2: Specify the URL
For On-Premise Setup
Use the following URL format:
https://<Saner CVEM Sever IP or Domain Name>/AncorWebService/perform
Example:
https://172.16.16.17/AncorWebService/perform
For Cloud Setup
Use the default cloud URL:
https://saner.secpod.com/AncorWebService/perform
Note:
If you are using the cloud version, ensure that the IP address of the device executing the API request is whitelisted in the cloud environment.
Navigate to the Authorization section in your API client.
Select API Key as the authorization type.
In the Header section, add the following key-value pair:
Key: Authorization
Value: SAML <Your SAML Key>
Use the portion of the key that follows the term SAML, ensuring there is a space after “SAML”.
Step 4: Configure the Body Section
Go to the Body tab in your API client.
Choose raw as the input type.
Select JSON as the format.
Enter the API request parameters in JSON format as per your requirement.
Refer to the official API documentation for the correct parameter structure and supported operations.
Step 5: Send the Request
Once all required fields are configured, click the Send button in your API client.
The response to your API request will be displayed in the Response section of the tool.
Additional Notes
Ensure that the Saner CVEM server or cloud service is reachable from your network.
Verify the SAM key and URL format to preve
nt authorization or connectivity issues.
For detailed API structures, request parameters, and supported endpoints, refer to the official Saner CVEM API documentation.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article