---
title: Authentications per Application
description: Track the number of successful application sign-ons per PingOne environment over time to measure application usage and adoption trends
component: pingone-api
page_id: pingone-api:platform:authentications-per-application/index
canonical_url: https://developer.pingidentity.com/pingone-api/platform/authentications-per-application/index.html
llms_txt: https://developer.pingidentity.com/pingone-api/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: 2026-08-11
section_ids:
  assigning-admin-roles-and-permissions-to-this-service: Assigning admin roles and permissions to this service
  authentications-per-application-data-model: Authentications per application data model
  response-codes: Response codes
---

# Authentications per Application

The authentications per application service calculates the number of successful sign-on actions for all applications in a specified environment during a specified time period. This metric shows how often applications are accessed, using authentications as the measure of the application's usage. Organizations can use this metric to:

* Determine which applications are responsible for the highest volume of authentication requests, in rank order.

* Refer to which applications are rarely used and are candidates for decommission.

* Refer to the relative number of authentication requests for each connected application.

* Determine whether an application's usage is growing or shrinking over time.

* View the total number of authentication requests per application over time.

The count of successful authentications is the total number of `FLOW.UPDATED` events with `COMPLETED` status during the specified period.

For example, suppose you want to see the number of authentications (per application) per day for a three-day period starting on September 1, 2019. Requests to this service require the following filter parameter to define the query:

* `occurredAt`

  Specifies the start date for the period of interest. For this example, to specify a date range starting on September 1, 2019, the value is `occurredAt ge "2019-09-01T00:00:00Z"`.

Requests to this service also require the following query parameters to define the query:

* `samplePeriod`

  Specifies the time interval in hours. For this example, to specify a daily interval, the value is `samplePeriod=24`.

* `samplePeriodCount`

  Specifies the number of sample periods. For this example, to specify three days of results, the value is `samplePeriodCount=3`.

The authentications per application service supports `limit` as an optional query parameter to specify a subset of applications returned in the response. For information about limiting collections, refer to [Conventions](../../foundations/conventions/index.html).

## Assigning admin roles and permissions to this service

Admin role assignments determine access to PingOne APIs. When assigning admin roles to this service, refer to [PingOne Permissions by Service](../reference/roles-and-permissions-in-pingone/permissions-by-service.html) for the service-specific permissions.

You can also choose to assign admin roles based on particular service resources. Refer to [PingOne Permissions by Resource](../reference/roles-and-permissions-in-pingone/permissions-by-resource.html) when assigning admin roles per service resources.

Admin assignments to roles are set by:

* [Automatic assignment for some roles](../roles/predefined-roles/index.html#automatic-role-assignment).

* [Group Role Assignments](../group-role-assignments/group-role-assignments.html).

* [User Role Assignments](../users/user-role-assignments/index.html).

Refer to [Roles Management](../roles/index.html) for more information.

## Authentications per application data model

| Property    | Type    | Required | Mutable | Description                                                                                                                                                                                            |
| ----------- | ------- | -------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `endDate`   | Date    | Required | Mutable | The date and time the authentication data collection ends (ISO 8601 format).                                                                                                                           |
| `partial`   | Boolean | Optional | Mutable | Indicates the partial period. When visible in the response data and set to `true`, this indicates that the response represents a shorter duration than requested through the `samplePeriod` parameter. |
| `signons`   | Integer | Required | Mutable | The number of authentications for the application identified by its application ID between the start and end dates of the sample period.                                                               |
| `startDate` | Date    | Required | Mutable | The date and time the authentication data collection starts (ISO 8601 format).                                                                                                                         |

## Response codes

| Code | Message                                                               |
| ---- | --------------------------------------------------------------------- |
| 200  | Successful operation.                                                 |
| 400  | The request could not be completed.                                   |
| 401  | You do not have access to this resource.                              |
| 403  | You do not have permissions or are not licensed to make this request. |
| 404  | The requested resource was not found.                                 |
| 500  | Internal server error.                                                |