Delete a milestone

Soft-deletes the grouping. The projects under it are left alone and fall back to no milestone — removing a grouping never takes work with it. Admin-only, and deliberately tighter than editing: the owner of a milestone can rename and recolor it, but retiring a grouping that other people’s work is filed under is the module admin’s call.

Required scope

The access token must carry this scope. A token missing it gets 403 Forbidden. Grant them to an API client under Settings → Company → API, and to a teammate under Employee → Permissions.

projects:admin

Path Parameters

Name	Type	Required	Description
`milestoneId`	string	Required	Milestone ID.

DELETEExample request

curl

curl -X DELETE "https://www.pxb.app/api/public/v1/milestones/{milestoneId}" \
  -H "Authorization: Bearer your_access_token"

200Example response

json

{
  "message": "Milestone deleted successfully!",
  "content": {
    "milestoneId": "epc_9f8e"
  }
}

In the console

The same thing done by hand, for anyone comparing the API against the screen they already use.

Projects → Milestones

/projects