Resolve a file integrity alert
curl --request POST \
--url https://my.propops.app/api/security/resolve-alert \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"alert_id": 1,
"csrf_token": "abc123def456",
"notes": "File was updated as part of release v2.1.0."
}
'{
"success": true,
"message": "Operation completed successfully"
}File Integrity
Resolve a file integrity alert
Mark a file integrity alert as resolved with optional notes. Required permission: api.security.resolve_alert.manage
POST
/
api
/
security
/
resolve-alert
Resolve a file integrity alert
curl --request POST \
--url https://my.propops.app/api/security/resolve-alert \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"alert_id": 1,
"csrf_token": "abc123def456",
"notes": "File was updated as part of release v2.1.0."
}
'{
"success": true,
"message": "Operation completed successfully"
}Documentation Index
Fetch the complete documentation index at: https://help.propops.app/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
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...Body
application/json
⌘I