This article explains how to retrieve the application's ID to use with API calls or System Log queries and why this is needed.

• Application ID

When creating users and applications in Okta, an ID is assigned to each user/application created. The ID is used to identify the application/user in internal and external contexts and may be used as an external ID user attribute for mapping, application username, etc. 

Okta User and Application IDs are pseudo-randomly generated on user creation and unique across all Okta tenants and cells.

Follow the video or the steps below.

1. Log in to the Admin dashboard and navigate to Applications. Search for and select the application.

2. Note the URL shown in the browser's address bar. It should be in the following format:
   https://company-admin.okta.com/admin/app/<APPLICATION_NAME>/instance/<APPLICATION_ID>/
   
    

3. Take note of <APPLICATION_ID> based on the example format. The same ID can be viewed in the syslog search bar after clicking the View Logs link on the application page.

4. This can be used in Application API Calls, such as Get application, and in System Log filters, such as "target." id.
   
   For example:

• • The app ID in a System Log search filter can be used:

target.id eq "0oagcc123546886ABC" and target.type eq "AppInstance"

• • Or in an API Call:

GET /api/v1/apps/0oagcc123546886ABC
 

Relates 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