Skip to main content

​
PATCH /api/modules//deactivate

Deactivates a module, changing its status to INACTIVE. Deactivated modules are not available for use in the authorization service.

​
Authentication

Requires authentication with valid JWT token.

​
Path Parameters

​
id
UUID
required
The unique identifier of the module to deactivate

​
Response

Returns no content on success (HTTP 204).

​
Status Codes

  • 204 No Content - Module deactivated successfully
  • 404 Not Found - Module not found

​
Example Request

curl -X PATCH https://api.example.com/api/modules/550e8400-e29b-41d4-a716-446655440000/deactivate \
  -H "Authorization: Bearer YOUR_JWT_TOKEN"

​
Example Response

No content returned (HTTP 204)

​
Error Response

{
  "timestamp": "2026-03-04T10:30:00Z",
  "status": 404,
  "error": "Not Found",
  "message": "Module not found with id: 550e8400-e29b-41d4-a716-446655440000",
  "path": "/api/modules/550e8400-e29b-41d4-a716-446655440000/deactivate"
}

​
Notes

  • This operation is audited with action type “DESACTIVAR_MODULO”
  • After deactivation, the module status will be set to INACTIVE
  • Use the Get Module endpoint to verify the status change
  • Deactivated modules may still exist in the system but cannot be used for authorization

Build docs developers (and LLMs) love

Get started for freeTalk to us