get-usages
Retrieve usage analytics including compute units consumed and assets generated, with filtering by user, project, time range, and activity type.
Instructions
Provide usage data for the given filters. Such as consumed compute units, number of assets generated, etc. Maximum time range with custom startDate and endDate is 120 days. Granularity is calculated based on the time range.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| userId | No | The unique identifier of the user for the usage. If not provided, returns all usages for the team. | |
| activityOffset | No | The offset for the activity data. Default is 0. If bad offset or empty, 0 will be returned. Must be a positive integer. | |
| userIds | No | The unique identifiers of the users for filtering the usage data. If not provided, use all users. Can be one or more comma separated values. | |
| type | No | The type of the usage data. Can be one or more comma separated values. Default is all types. If bad type or empty, all types will be returned. | |
| endDate | No | The end date of the usage in ISO 8601 format. If not provided, use default timeRange. If provided, startDate is required. | |
| projectIds | No | The project ids for filtering the usage data. If not provided, use all projects. Can be one or more comma separated values. | |
| timeRange | No | The time range of the usage. If not provided, use default timeRange. If startDate and endDate provided, timeRange is ignored. | |
| startDate | No | The start date of the usage in ISO 8601 format. If not provided, use default timeRange. If provided, endDate is required. |