List Applications

post

https://api-ext.zluri.com/v2/applications

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

Supported Filters:

Field	Type	Description / Allowed Values
`app_name`	string	Application name
`app_id`	string	Application ID
`app_authorization_status`	enum	`restricted`, `needs review`, `centrally managed`, `team managed`, `individually managed`, `unmanaged`
`app_status`	enum	`active`, `inactive`
`app_type`	enum	`application`, `website`, `device`, `browser`, `other`
`app_owner_id`	string	Application owner ID
`app_owner_email`	string	Application owner email
`app_technical_owner_id`	string	Technical owner ID
`app_technical_owner_email`	string	Technical owner email
`app_financial_owner_id`	string	Financial owner ID
`app_financial_owner_email`	string	Financial owner email
`app_category`	string	App category name
`app_sub_category`	string	App sub category ID
`app_archive`	boolean	Is Archived
`app_is_custom`	boolean	Is Custom
`app_chargeback`	string	Chargeback
`app_discovered`	range	Discovered On (date range)
`app_last_used`	range	Last Used (date range)
`app_usage`	number	Application usage
`app_threat_level`	number	Maximum risk score
`source_array`	object	Sources
`primary_source_array`	object	Primary Source
`sso_source_array`	object	SSO Source
`agent_source_array`	object	Agent Source
`app_logo_present`	boolean	Whether 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).