⚠️ This documentation is not complete and will change. Documentation and API References are actively being updated.
curl --request POST \
--url https://api.propops.app/api/security/sessions \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"action": "terminate",
"csrf_token": "abc123def456",
"session_id": "sess_001",
"user_id": 1,
"reason": "Suspicious activity detected."
}
'{
"success": true,
"message": "Operation completed successfully"
}Perform session management actions:
terminate — End a specific user session (requires api.security.sessions.terminate)blacklist_add — Add a user to the access blacklistblacklist_remove — Remove a user from the blacklistcurl --request POST \
--url https://api.propops.app/api/security/sessions \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"action": "terminate",
"csrf_token": "abc123def456",
"session_id": "sess_001",
"user_id": 1,
"reason": "Suspicious activity detected."
}
'{
"success": true,
"message": "Operation completed successfully"
}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...