List Applications

This endpoint fetches application data based on filters like name, status, type, state, and usage metrics. Supports pagination and sorting.

Supported Filters:

FieldTypeDescription / Allowed Values
app_namestringApplication name
app_idstringApplication ID
app_authorization_statusenumrestricted, needs review, centrally managed, team managed, individually managed, unmanaged
app_statusenumactive, inactive
app_typeenumapplication, website, device, browser, other
app_owner_idstringApplication owner ID
app_owner_emailstringApplication owner email
app_technical_owner_idstringTechnical owner ID
app_technical_owner_emailstringTechnical owner email
app_financial_owner_idstringFinancial owner ID
app_financial_owner_emailstringFinancial owner email
app_categorystringApp category name
app_sub_categorystringApp sub category ID
app_archivebooleanIs Archived
app_is_custombooleanIs Custom
app_chargebackstringChargeback
app_discoveredrangeDiscovered On (date range)
app_last_usedrangeLast Used (date range)
app_usagenumberApplication usage
app_threat_levelnumberMaximum risk score
source_arrayobjectSources
primary_source_arrayobjectPrimary Source
sso_source_arrayobjectSSO Source
agent_source_arrayobjectAgent Source
app_logo_presentbooleanWhether app logo is present

Date Range Filter Format: For filtering by date/time fields, use the field_order parameter to specify comparison operators:

Date Range Filter (Between two dates):

{
  "field_id": "app_discovered",
  "field_values": ["2025-11-12", "2025-11-13"],
  "field_order": ["gte", "lte"]
}

Single Date Comparison:

{
  "field_id": "app_last_used",
  "field_values": ["2025-11-12"],
  "field_order": ["gte"]
}

Available Field Order Operators:

  • gte - Greater than or equal to
  • lte - Less than or equal to
  • eq - Equal to
  • ne - Not equal to
  • lt - Less than
  • gt - Greater than

Custom Fields Filter Format:

{
  "field_id": "custom_fields",
  "field_values": {
    "custom_field_id": "679b613f315ee0a11cb67bd1",
    "custom_field_values": ["India"]
  }
}

Use these as field_id values inside the filter_by array in the request body to filter results. For custom fields, the field_id will always be custom_fields, while the field_values object must contain custom_field_id (the ID of the custom field) and custom_field_values (an array of values to filter by).

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
string

The page parameter determines which set of data is returned in a paginated response. Start from page 0 to retrieve the first set of results.

string

The page_size parameter specifies the number of results per page. The default is 50. Maximum is 100.

string

Comma-separated keywords to search in user names.

Body Params
filter_by
array of objects

Filters to apply on applications data. Supports both standard fields and custom fields with various data types and operators.

filter_by
sort_by
array of objects

Sort options for the results

sort_by
Headers
string
required

API key for authentication

Responses

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json