-
Notifications
You must be signed in to change notification settings - Fork 639
Description
Problem
When reviewing the steps outlined on this page: https://developer.okta.com/docs/reference/rest/
Step 4, shows the following:
In the Import dialog, paste the following link into the Paste cURL, Raw text or URL... textbox: https://developer.okta.com/docs/api/postman/example.oktapreview.com.environment.
When looking at the file (brief excerpt):
{
"id": "1352452f-4532-293c-5707-f626e6a989aa",
"name": "{yourOktaDomain}",
"values": [
{
"key": "url",
"value": "https://{yourOktaDomain}",
"type": "text",
"name": "url",
"enabled": true
},
{
"key": "apikey",
"value": "",
"type": "text",
"name": "apikey",
"enabled": true
},
We see the following details for the keys.
However, later on in the step for Importing a Collection
, most of the references no longer work:


Meaning the references and the documentation are not in sync, and cause a massive pain when working with Postman.
Could this be cleaned up, organized so that this works smoothly? It's a massive pain, when the Postman Collection, appears to have the most up to date / complete API resource.
While the url and apikey are two examples, it goes much further then that. The Postman Collection also includes :policyid
, meaning that this can't be filled in using environment variables.

Potential Resolution
Work towards aligning both the environment file and the API collection to work properly with the environment file.
Second potential resolution, make it easier to use either OpenID/OAuth2 in Postman and/or API Keys - as when switching to API Keys to try to obtain some API data, it responds incorrectly.