View Application Events with REST API (version 2.0)

Use APPLICATION_EVENTS to return application events which report errors or check how often someone used a feature in your application, like accessing the online help. You create an application event in the Aternity Activity Designer and upload it to Aternity as a custom activity.

Each returned entry from APPLICATION_EVENTS contains one reported application event, with its category, details and time (if applicable), along with the application, user and device details.

There are three types of application events (displayed in the Event_Type field):

  • Application Usage Duration is for measuring the time to complete a non-typical complex business activity, like one which includes application response times mixed with time waiting for the user. For example, use this to measure the time required for a user to identify a customer at the beginning of a call.

    The returned Event_Duration field displays the time for the event to complete.

  • Application Usage Event is for counting the times when an event occurred, or when it is not easy to identify the end event of an activity. For example, if you want to track the number of times when people shared their desktop in Skype for Business, track this as an application usage event, and assign a Category to different types of usage events.

  • Application Error Events are for tracking the occurrence of errors. Each error has a Category, or type of error, and a Details field, which contains details of the event or error.

    See the returned Event_Category and Event_Details fields.

Count a custom application event

About how long Aternity keeps this data (retention) and how far back you can go, read here.


This article covers the latest REST API version. For older version 1.0, click here.

Before You Begin

To send a REST API query in Excel, PowerBI or a browser, enter the URL of the REST API, your Aternity username (must have the OData REST API role) and its password. You can find this by selecting User icon > REST API Access. SSO users must generate (once) and use a special password, as Aternity's REST API does not authenticate with your enterprise's identity provider. For LDAP users, enter the domain name, then a backslash ('\'), then your network username and password. For example domain_name\jsmith

To view Aternity REST API, enter the base URL from Aternity > User icon > REST API Access, followed by the name of the API into a browser, Excel or PowerBI (learn more). For VIEWING, use <base_url>/latest/API_NAME; for INTEGRATIONS, use <base_url>/<version number>/API_NAME (for example, <base_url>/v1/API_NAME, or <base_url>/v1.0/API_NAME, or <base_url>/v2/API_NAME, or <base_url>/v2.0/API_NAME).

Get the latest REST API version for analyzing in the external app
The <base_URL> is configured in the Aternity REST API Server as the external_url (learn more):

Wherever possible, use $select and $filter to narrow your query, to avoid receiving an error like Returned data is too large. Learn more.


To access this API from a browser, Excel or Power BI (learn more), enter <base_url>/latest/APPLICATION_EVENTS or <base_url>/v2/APPLICATION_EVENTS

To view the users who experienced application events in the last six hours from devices with hard disk drives (not SSDs) in Miami or Los Angeles, that experienced IO write times lower than 10,000 MB/sec, by using this filter:

.../APPLICATION_EVENTS?$select=username&$filter=relative_time(last_6_hours) and OS_DISK_TYPE eq 'HDD' and (contains(LOCATION_CITY,'Angeles' or LOCATION_CITY eq 'Miami')

Supported Parameters

You can view the data by entering the URL into Excel, into a browser, or into or any OData compatible application such as Power BI.

You can add parameters to the URL to filter the returned data, by adding a question mark (?) followed by a parameter and value, such as .../API_NAME?$filter=(USERNAME eq ''), or several parameter-value pairs each separated by an ampersand (&), like .../API_NAME?$format=xml&$top=5.

Query Options Description

Use $select to return only specific columns (attributes), to make queries more efficient: ...API_NAME?$select=COL1,COL2,COL3


Use $format to force the returned data to be either in XML or JSON format. This is only useful for testing the raw data in a web browser. For example: .../API_NAME?$format=xml


Use $orderby to sort the returned data according to the value you choose. For example, .../API_NAME?$orderby=LOCATION


Use $top (lower case only) when you are initially testing the response of the API by returning the first few entries.

For example, to return the first five entries (not sorted), use: ...API_NAME?$top=5


Use $filter to insert conditions that narrow down the data, to return only entries where those conditions are true..

To limit the timeframe of a query, add $filter=relative_time() like, .../API_NAME?$filter=relative_time(last_x_hours) or (last_x_days). Learn more.

Create conditions for filtering with any of the following operators:

Query Operators Description

Equal to

For example, COL4 eq 'val4'


Not equal to

For example, COL4 ne 'val4'


Greater than

For example, COL4 gt 'val4'


Greater than or equal

For example, COL4 ge 'val4'


Less than

For example, COL4 lt 'val4'


Less than or equal

For example, COL4 le 'val4'


Logical and

For example, COL1 eq 'value1' and COL2 ne 'value2'


Logical or

For example, COL1 eq 'value1' or COL2 ne 'value2'


Logical negation

Create conditions for filtering with any of the following functions:

Query Functions Description

For example, $filter=startswith(account_name,'Aternity')


For example, $filter=endswith(account_name,'Aternity')



For example, $filter=contains(account_name,'Aternity')

Use operators with parentheses to group conditions logically: .../API_NAME?$filter=(COLUMN1 eq 'value1' or COL2 neq 'val2') and (COL3 gt number) and not (COL4 eq 'val4' or contains(COL5,'val5'))
$search is NOT supported.

Do not use $search in Aternity's REST APIs.


Wherever possible, use $select and $filter to narrow your query, to avoid receiving an error like Returned data is too large. Learn more.


Each returned entry from APPLICATION_EVENTS contains one reported application event, with its category, details and time (if applicable), along with the application, user and device details.

The API returns two types of columns: Attributes (or dimensions) which are the properties of an entry, and Measurements which are the dynamic measured values.

Type Returned columns




Account_ID,Account_Name,Activity_Name,Activity_Page_Title,Application_Name,Application_Type,Application_Version,Browser,Business_Location,Calendar_Date,Calendar_Month,Calendar_Week,Client_Device_Name,Client_Device_Type,Corp_Channel,Corp_Line_Of_Business,Corp_Market,Corp_Store_ID,Corp_Store_Type,Custom_Attribute_1 - 9,Custom_Pilot_Group,Data_Center_Business_Location,Device_CPU_Cores,Device_CPU_Frequency,Device_CPU_Generation,Device_CPU_Model,Device_CPU_Type,Device_Days_From_Last_Boot,Device_ID_Mobile_Or_Mac,Device_Image_Build_Number,Device_IP_Address,Device_Manufacturer,Device_Memory,Device_Model,Device_Name,Device_Network_Type,Device_Power_Plan,Device_Subnet,Device_Type,Event_Category,Event_Details,Event_Duration,Event_Type,Location_City,Location_Country,Location_On_Site,Location_On_VPN,Location_Region,Location_State,Measurement_Start_Timestamp,Mobile_Carrier,MS_Office_License_Type,MS_Office_Version,OS_Architecture,OS_Disk_Type,OS_Family,OS_Name,OS_Version,Server_Hostname,Server_IP,Server_Name,Timeframe,User_Department,User_Domain,User_Email_Address,a_conrefs_odata_columns_v2.html#glossentry_kf5_x3y_rcb_v2,User_Office,User_Role,User_Title,Username,Virtualization,Wifi_BSSID,Wifi_Channel,Wifi_SSID,