⚠️ This documentation is not complete and will change. Documentation and API References are actively being updated.
curl --request GET \
--url https://api.propops.app/api/admin/settings-stats \
--header 'Authorization: Bearer <token>'{
"success": true,
"message": "Operation completed successfully",
"data": {
"users_total": 123,
"users_active": 123,
"users_inactive": 123,
"branches": 123,
"tenants": 123,
"active_sessions": 123,
"blacklisted_sessions": 123,
"job_documents": 123,
"password_breaches": 123,
"integrity_issues": 123,
"cron_jobs": 123,
"notices": 123,
"api_endpoints": 123,
"activity_logs": 123,
"email_logs": 123
}
}Returns aggregate statistics for the admin settings dashboard including user counts, branch counts, active sessions, security metrics, and more.
Required permission: api.admin.settings_stats.manage
curl --request GET \
--url https://api.propops.app/api/admin/settings-stats \
--header 'Authorization: Bearer <token>'{
"success": true,
"message": "Operation completed successfully",
"data": {
"users_total": 123,
"users_active": 123,
"users_inactive": 123,
"branches": 123,
"tenants": 123,
"active_sessions": 123,
"blacklisted_sessions": 123,
"job_documents": 123,
"password_breaches": 123,
"integrity_issues": 123,
"cron_jobs": 123,
"notices": 123,
"api_endpoints": 123,
"activity_logs": 123,
"email_logs": 123
}
}All API requests must include a valid Bearer token in the Authorization header.
Tokens are 64-character SHA-256 session hashes issued by the PropOps authentication system.
Example:
Authorization: Bearer a1b2c3d4e5f6...