

Use this collection to generate an access_token that can be used to make requests using the other collections. Variable names are wrapped in environment variable has been set based on the subdomain for the account being used.Ĭollections for version 2 APIs can be found here.
#Postman install all users download
Download and open a OneLogin Postman Collection. Identify the environment variables that you want to define. If you do not already have Postman installed, install it. Setting up the environment variables requires some upfront work, but will make repeated use of the Postman Collections a lot more convenient. For example, you’ll create environment variables to provide values for your client ID and secret, data shard, access token, subdomain, and so forth. Why don’t the Postman Collections include these values as delivered? This is because the values are unique, and even private, to your OneLogin account environment. You’ll use these environment variables to set values that Postman needs to make an API call. To use the Postman Collections provided further down this page (and on each individual API doc page), you’ll need to set up environment variables in Postman. Once you’ve familiarized yourself with the API’s behavior, switch over to using your production OneLogin account and API credentials. Try it out with a test account first: Start off using a Postman Collection with a test OneLogin account and API credentials.

Download a Postman Collection that provides all of the calls available for each of our OneLogin resources.
