Okta assigns a unique, pseudo-randomly generated ID to each application upon creation to identify it in both internal and external contexts. Application Programming Interface (API) calls, external ID user attribute mappings, and System Log queries require this identifier. Administrators can get the application ID directly from the application URL in the Admin Console or through the System Log search bar.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Application ID
• Application Programming Interface (API)
• System Log

How can administrators find the application ID for an application in Okta?

Navigate to the application in the Admin Console to extract the unique identifier from the browser URL, or locate it in the System Log search bar, as detailed in the video demonstration or the written instructions.

1. Sign in to the Okta Admin Console and navigate to Applications.

2. Search for and select the application.
3. Review the URL shown in the browser address bar. The URL follows a specific format containing the application ID.

   https://<subdomain>-admin.okta.com/admin/app/<application_name>/instance/<application_id>/

4. Extract the <application_id> from the URL based on the example format. Alternatively, view the exact ID in the System Log search bar after selecting the View Logs link on the application page.

How can Okta administrators use the application ID in API calls and System Log queries?

Utilize the extracted application ID to filter System Log events or execute Application API calls.

• Use the application ID in a System Log search filter:

  target.id eq "<application_id>" and target.type eq "AppInstance"

• Use the application ID in Application API Calls, such as Get application:

  GET /api/v1/apps/<application_id>

   

Related References

• How to obtain a report of application External IDs using Postman
• Can the Okta User ID be Used for Profile Mappings
• Will the Okta User ID or Application ID be Unique Across all Okta Instances