Search and Filter by Fields in Auth0 Dashboard

Search and filter Auth0 resources by name, ID, type, and metadata in Auth0 Dashboard.

Auth0 provides tenant users a more intuitive search capability for registered Applications and APIs with the ability to build filter expressions for searchable fields in Auth0 Dashboard. Rather than scroll through paginated lists with hundreds of resources, your tenant user queries for fields such as:

• The name of your application (Travel0-native)
• Application or user metadata (permissions)
• Application type (SPA)
• API by name
• API by ID

Auth0 Dashboard returns matching results in real time from all your registered resources.

How it works

The search bar on the Applications and the APIs section of Auth0 Dashboard uses a guided filter interface and Boolean search. The search bar functions as a dropdown menu that lists the filterable fields. When you select a field and enter a value, the filter applies the value as a removable tag above the results. You can combine up to five filters at a time.

Each filter you add narrows results further. To specify results, apply AND/OR logic between different fields. Filters reflect in the URL as query parameters. Copy the URL at any point to share with a teammate or bookmark it to return to the same filtered view later.

Boolean example

If you filter by Application type Native OR SPA, and First-party client true, the results show only first-party applications that are either Native or SPA. Applications that are Regular Web Apps or third-party apps are excluded.

Search behavior by field type

Auth0 Dashboard search matches results based on the field type.

• String fields (name, identifier): Partial match is supported. Entering payments finds “Payments-application”, “Corp Payments Service”, and similar — word order does not matter. To exclude results that match a term, prefix it with NOT, -, or No — for example, entering NOT test in the name field returns all resources whose name does not contain “test”. Wildcard searches require at least three characters; entering fewer shows a “Minimum 3 characters” message and does not submit the query.

• Exact match fields

You must enter the full ID value. Partial IDs return no results. Use these fields when you have a specific Client ID from a log or support ticket.

• Metadata fields

You can search metadata by key and value or by key only:

• Key and value: Enter a key and a value to find resources where that exact key matches that value. For example, key environment and value production returns only resources where app_metadata.environment equals production. Prefix matching is supported for values — entering prod matches production, prod-eu, and prod-us.
• Key only: Enter a key and press Enter without a value. This returns all resources that have that metadata key set, regardless of its value. Useful for finding resources that use a specific key at all.

You can also search nested metadata keys up to two levels deep using dot notation. For example, key tier.bronze and value true matches resources where app_metadata.tier.bronze equals true.

To exclude results that match a specific key-value pair, prefix the value with NOT. For example, key color and value NOT orange returns all resources where color is set to anything other than orange. Keys must be an exact match. Contains and ends-with matching are not supported for metadata. Values are indexed up to 64 characters, longer values are not searchable.

• Enum fields

Select one or more Application types from a predefined list. Multiple selections within the same filter use OR logic. For example, select Native and SPA returns all Native and SPA applications.

• Boolean fields

Search for first-party clients by selecting true or false. Use this to distinguish first-party applications (those authorized to skip the consent screen) from third-party ones.

Searchable fields

Applications

Field	Description	Match type
Name	The name of the application	Partial match
Client ID (client_id)	The unique client ID	Exact match
External client ID (external_client_id)	An external identifier for the application	Exact match
Metadata	Custom key-value metadata stored on the application	Exact or prefix match
Application type	Native, SPA, Regular Web App, or Machine to Machine	Enum selection
First-party client	Whether the application is first-party or third-party	Boolean

APIs

Field	Description	Match type
Name	The name of the API	Partial match
Identifier	The unique audience identifier (for example, https://api.example.com)	Partial match
Id	The internal system ID	Exact match

Limitations

• You can apply a maximum of five filters per search. The search bar prevents adding a sixth filter.
• Search results may not reflect changes made in the last few seconds, as the index is eventually consistent.
• Results return within two seconds under normal conditions. If a query times out, reduce the number of filters or use a more specific search term.

Example queries

Find an application by client ID

Use this when you have a client_id from an error log or support ticket and need to locate the application quickly.

1. Navigate to Auth0 Dashboard > Applications > Applications.
2. Select the search bar and choose Client ID.
3. Paste the full client_id value. The matching application appears immediately.

Find applications using metadata

If your applications store custom metadata — such as environment labels, plan tiers, or external IDs — you can search by those values.

1. Navigate to Auth0 Dashboard > Applications > Applications.
2. Select the search bar and choose Metadata.
3. Enter the metadata key, for example environment.
4. Enter the value, for example production. Applications where metadata.environment equals production appear in the results. To match by prefix, enter a partial value such as prod.

Troubleshooting

No results found

Check that the filter values are spelled correctly. For string fields, try a shorter or more general term. For metadata fields, confirm the exact key name — keys are case-sensitive and must be an exact match. Contains-style matching is not supported for metadata; use a prefix instead. For exact match fields such as Application ID, make sure you are pasting the complete ID value.

Results seem outdated

Search results are eventually consistent and may not reflect changes made in the last few seconds. If you recently created or updated a resource, wait a few seconds and retry the search.

Search timed out

Reduce the number of active filters or use a more specific search term. If the problem persists, contact Auth0 Support.