License Provisioning Setup via REST HTTP/SSL Endpoint

Production endpoint

https://integrations-api.pluralsight.com/provision

Authentication options

Basic Authentication

Username: pluralsight

Password: [insert-your-api-key-here]

Bearer Authentication

Set Authentication header to Bearer [insert-your-api-key-here]

HTTP Method: POST

You will provide a CSV file containing all users that you want to provision. By default, the provision process is run as a "dry run", meaning the operations to remove user licenses in Pluralsight would be generated and stored but not applied. This allows for a review of the data to ensure everything would appear the way you expected. To apply the operations, a dryRun parameter in the URL will need to be set to false. See the "Turning off Dry Run" section below.

Headers

Content-Type: text/csv

Content-Disposition: attachment; filename="provision.csv"

Body

You must provide the provision CSV file. Details follow.

Provision CSV File

File Name: provision.csv

File Data:

• Format as CSV
• Fields
  • id: any unique identifier for a worker (strongly prefer id used for SSO integration with Pluralsight)
  • email: user’s email.
  • first_name: user’s first name.
  • last_name: user’s last name.

Please filter out any users that are missing ids or emails. These fields are required and will cause an error if they are missing. All users must have a unique id and a unique email

Please Note: The use of special characters in files (Quotation marks, commas, symbols, etc.) can possibly cause errors while parsing. We recommend that you remove any special characters from your files to ensure your file gets processed successfully.

To view available URL parameters and possible responses, please visit the URL Parameters and Responses page