Delete Category

​

Endpoint

DELETE /api/categories/:id

​

Authentication

​

Path Parameters

​

Response

​

Example Request

curl -X DELETE https://api.yourapp.com/api/categories/987fcdeb-51a2-43e7-9abc-123456789def \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "X-CSRF-Token: YOUR_CSRF_TOKEN"

​

Example Response

{
  "success": true,
  "message": "Categoría eliminada correctamente"
}

​

Error Responses

{
  "success": false,
  "message": "Categoría no encontrada"
}

​

Related Endpoints

​

Get Orphaned Transaction Count

GET /api/categories/:id/orphaned-count

​

Example Request

curl -X GET https://api.yourapp.com/api/categories/987fcdeb-51a2-43e7-9abc-123456789def/orphaned-count \
  -H "Authorization: Bearer YOUR_TOKEN"

​

Example Response

{
  "success": true,
  "count": 15
}

​

Reassign Transactions

POST /api/categories/:id/reassign

​

Request Body

​

Example Request

curl -X POST https://api.yourapp.com/api/categories/987fcdeb-51a2-43e7-9abc-123456789def/reassign \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -H "X-CSRF-Token: YOUR_CSRF_TOKEN" \
  -d '{
    "to_category_id": "456789ab-cdef-1234-5678-90abcdef1234"
  }'

​

Example Response

{
  "success": true,
  "message": "Transacciones reasignadas: 15",
  "reassignedCount": 15
}

​

Reassign Error Responses

{
  "success": false,
  "message": "to_category_id es requerido"
}

{
  "success": false,
  "message": "Categories must belong to the same account"
}

{
  "success": false,
  "message": "Source category not found"
}

{
  "success": false,
  "message": "Destination category not found"
}

​

Recommended Workflow

1. Check orphaned count: Use GET /api/categories/:id/orphaned-count to see how many transactions will be affected
2. Reassign if needed: If transactions exist, use POST /api/categories/:id/reassign to move them to another category
3. Delete category: Finally, use DELETE /api/categories/:id to remove the category

​

Notes

• Deleting a category automatically sets subcategory_id to NULL for all associated transactions
• The database uses ON DELETE SET NULL constraint for this behavior
• Subcategories associated with the category are also deleted (cascade delete)
• The user must own the category or have access to the associated account
• Consider using the reassign endpoint to preserve transaction categorization