Skip to main content

​
PATCH /api/permissions//activate

Activates a permission that was previously deactivated, making it available for assignment to roles.

​
Authentication

This endpoint requires authentication with a valid Bearer token.

​
Path Parameters

​
id
uuid
required
The unique identifier of the permission to activate

​
Response

This endpoint returns no content on success (HTTP 204).

​
Status Codes

  • 204 No Content - Permission activated successfully
  • 404 Not Found - Permission with the specified ID not found
  • 500 Internal Server Error - Server error occurred

​
Example Request

curl -X PATCH https://api.example.com/api/permissions/550e8400-e29b-41d4-a716-446655440000/activate \
  -H "Authorization: Bearer YOUR_TOKEN"

​
Example Response

Successful activation returns HTTP 204 with no body.

​
Error Response

{
  "timestamp": "2026-03-04T10:30:00Z",
  "status": 404,
  "error": "Not Found",
  "message": "Permiso no encontrado",
  "path": "/api/permissions/550e8400-e29b-41d4-a716-446655440000/activate"
}

​
Audit Log

This operation is automatically logged in the system audit trail with:
  • Module: PERMISOS
  • Action: ACTIVAR_PERMISO

Build docs developers (and LLMs) love

Get started for freeTalk to us