Fork Okta Public API Collections Into a Local Environment
Last Updated:
Administration
Okta Classic Engine
Okta Identity Engine
Overview
The Okta API documentation requires users to fork the Okta Public API Collections workspace into a preferred workspace instead of adding individual collections to an environment. Fork the collection using the Postman web interface to import it into the desktop application.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Postman
Solution
What are the steps to fork Okta Public API Collections into a local environment?
Access the Okta Public API Collections workspace in a web browser, select an operation to reveal the authorization options, sign in with the Postman desktop account credentials, and fork the collection to synchronize it with the local desktop application.
- Navigate to Okta Public API Collections.
- Open any folder and select an operation in the Postman web session.
- Select the Authorization tab.
- Select Sign In at the top right of the screen and authenticate using the account associated with the Postman desktop application.
- Select Fork Collection.
- Open the Postman desktop application to verify the successful collection import.
