Usage-vs-cap reporting (per-user) or account-wide at-limit counts.
curl --request GET \
--url https://pria.praxislxp.com/api/admin/usage-limits \
--header 'Authorization: Bearer <token>'{
"success": true,
"capsEnabled": true,
"accountWide": {
"used": 123,
"cap": 123,
"over": true
},
"perInstitution": {
"used": 123,
"cap": 123,
"over": true
},
"h24": {
"used": 123,
"cap": 123,
"over": true
},
"buckets": [
{
"start": "<string>",
"credits": 123,
"messages": 123
}
],
"totals": {
"credits": 123,
"messages": 123
}
}Admin Usage Limits
Usage-vs-cap reporting (per-user) or account-wide at-limit counts.
Two modes selected by query parameters:
userId+institutionId(orinstanceIdalias): one user’s usage-vs-cap gauges plus over-time{buckets, totals}(same shape as the user usage chart).accountId: account-wide counts of users/memberships at or over a cap.
GET
/
api
/
admin
/
usage-limits
Usage-vs-cap reporting (per-user) or account-wide at-limit counts.
curl --request GET \
--url https://pria.praxislxp.com/api/admin/usage-limits \
--header 'Authorization: Bearer <token>'{
"success": true,
"capsEnabled": true,
"accountWide": {
"used": 123,
"cap": 123,
"over": true
},
"perInstitution": {
"used": 123,
"cap": 123,
"over": true
},
"h24": {
"used": 123,
"cap": 123,
"over": true
},
"buckets": [
{
"start": "<string>",
"credits": 123,
"messages": 123
}
],
"totals": {
"credits": 123,
"messages": 123
}
}Authorizations
JWT token passed in authorization header
Query Parameters
Target user id (per-user mode; requires institutionId/instanceId).
Institution id for the per-user mode.
Alias for institutionId (forwarded by the usage chart).
Over-time window in days (per-user mode).
Account id (account-wide at-limit mode).
Was this page helpful?
⌘I