Skip to main content
DELETE
/
activities
/
{id}
Delete Activity
curl --request DELETE \
  --url https://api.example.com/activities/{id} \
  --header 'Authorization: <authorization>'
{
  "success": true
}
Deletes an activity by its ID.

Authentication

Authorization
string
required
Bearer token for authentication
Required Roles: monitor, admin

Path Parameters

id
number
required
The unique identifier of the activity to delete

Response

success
boolean
Indicates whether the deletion was successful

Example Request

curl -X DELETE https://api.sociapp.com/activities/10 \
  -H "Authorization: Bearer YOUR_JWT_TOKEN"

Example Response

{
  "success": true
}

Error Responses

401 Unauthorized

{
  "statusCode": 401,
  "message": "Unauthorized"
}

403 Forbidden

{
  "statusCode": 403,
  "message": "Forbidden resource"
}

404 Not Found

{
  "statusCode": 404,
  "message": "No se encontrĂ³ la actividad con id 10"
}

500 Internal Server Error

{
  "statusCode": 500,
  "message": "Failed to delete activity"
}

Important Notes

  • Deleting an activity does not automatically remove it from associated projects
  • Ensure that dependent records are handled appropriately before deletion
  • This operation cannot be undone

Build docs developers (and LLMs) love