Get Started with Permissions API

Everything you need to know to get started with the Permissions API.

Get a Visier account

To use the APIs, you must have a Visier account with a profile that has the API capability. If you don't have an account, contact your administrator. They will create an account for you with permissions that allow you to view data.

In addition to an API profile, your API user needs a profile with the following capabilities to use the Permissions API:

  • User Management: Write (access level), API (view level)
  • Security: Write (access level), API (view level)

Generate your API key and security token

To make an API request, you will need an API key and a security token. For more information about how to get an API key and request a security token, see API Authentication.

Note: If using Postman to send requests, you can request a security token directly in the tool, see Use Postman to Call Visier APIs.

Choose your tool

To use Visier APIs, you need to choose a tool to make your first request. This can be Postman or whichever method you usually use to make HTTP requests. For more information about using Postman for your first request, see Use Postman to Call Visier APIs.

Make your first request

To test that you have everything set up correctly, we'll create a request to retrieve all the permissions in your Visier solution using the /v1/admin/permissions endpoint. For a complete list of available endpoints, see "Permissions" in API Reference.

Replace {vanity_name} with your tenant name. The API key is expected as a header, while the security token is expected as a cookie.

Tip:  

To find your vanity name:

  1. In Visier, in the global workspace, click Settings > Single Sign-On.
  2. Under Single Sign-On, find your service provider endpoint; for example, https://jupiter.visier.com/VServer/auth. In this example, jupiter is the vanity name.
Copy
cURL sample request: Retrieve a list of all permissions
curl -X GET --url 'https://{vanity_name}.api.visier.io/v1/admin/permissions?tenantCode={tenantCode}' \
-H 'apikey:{api_key}' \
-H 'Cookie:VisierASIDToken={security_token}'

If everything was set up correctly and the request was successful, you should see a similar response:

Copy
Sample response
{
    "permissions": [
        {
            "permissionId": "ad07a919-187c-4ca7-b20a-9fc11996c6ce",
            "displayName": "HR Analytics",
            "description": "Detailed access to the workforce analytics module."
        },
        {
            "permissionId": "b066fdf7-426b-43b3-a55a-7e5239467409",
            "displayName": "Permission ABC"
        },
        {
            "permissionId": "29f98fd7-bc09-4378-a390-3ba4734cbf33",
            "displayName": "Recruiter Sales",
            "description": "Recruiters have detailed access to requisitions and applicants that hiring manager is in sales organization. "
        }
    ]
}

Next steps

Now that you've successfully authenticated and completed your first API request, you can call more Visier APIs!

Note: Permissions are versioned in Visier, meaning any permission changes through the API cause a project to publish to production with your changes. We recommend that you make permission changes sequentially and in bulk; for example, wait until your create call is successful before trying to update a permission. You can make up to 1000 definitions (create, update, delete) per API call.

To learn more: