Credit-cap gauges and block state for the caller's current institution.
curl --request GET \
--url https://pria.praxislxp.com/api/user/credit-cap-status \
--header 'x-access-token: <api-key>'{
"success": true,
"capsEnabled": true,
"blocked": true,
"perInstitution": {
"used": 123,
"cap": 123
},
"h24": {
"used": 123,
"cap": 123,
"resetAt": "2023-11-07T05:31:56Z"
},
"accountWide": {
"used": 123,
"cap": 123
}
}User
Credit-cap gauges and block state for the caller's current institution.
Returns the caller’s usage against any configured credit caps for their
current institution (and its parent account). capsEnabled is false when
caps are off or the user has no capped account; in that case the gauges
carry null caps. Reuses the same evaluator as server-side enforcement, so
the UI and the hard block agree exactly.
GET
/
api
/
user
/
credit-cap-status
Credit-cap gauges and block state for the caller's current institution.
curl --request GET \
--url https://pria.praxislxp.com/api/user/credit-cap-status \
--header 'x-access-token: <api-key>'{
"success": true,
"capsEnabled": true,
"blocked": true,
"perInstitution": {
"used": 123,
"cap": 123
},
"h24": {
"used": 123,
"cap": 123,
"resetAt": "2023-11-07T05:31:56Z"
},
"accountWide": {
"used": 123,
"cap": 123
}
}Authorizations
JWT token passed in x-access-token header
Response
200 - application/json
Cap status for the caller.
Available options:
h24, institution, account, null Which tier currently owns the caps for this user's institution.
Available options:
account, institution, none Show child attributes
Show child attributes
Show child attributes
Show child attributes
Show child attributes
Show child attributes
Was this page helpful?
⌘I