---
title: "Delete a success metric"
method: DELETE
path: "/api/v1/initiatives/{id}/success-metrics/{rootId}"
tags: ["Initiatives"]
---

# Delete a success metric

`DELETE /api/v1/initiatives/{id}/success-metrics/{rootId}`

## Request

- Base URL: `https://www.useboom.ai`
- URL: `https://www.useboom.ai/api/v1/initiatives/{id}/success-metrics/{rootId}`
- Auth: HTTP bearer

Retire a success metric. It disappears from the dashboard immediately — including from past periods, because successes are recalculated on every read, so the numbers this metric reported for earlier conversations go with it. The configuration is kept for the audit trail and success_metrics_list can still show it with `status: all`; adding the metric back with the same rootId restores it. Deleting the last metric returns the initiative to having no success measure, which is a normal state, not an error.

## Path parameters

- `id` string, required: The initiative id.
- `rootId` string, required: The metric to retire, as returned by success_metrics_list.

## Response `200`

Success

- object
  - `rootId` string, required
  - `deactivated` true, required

## Other responses

- `400`: Validation failed or the request cannot proceed.
- `401`: Missing, malformed, or revoked API key.
- `404`: The resource does not exist in this organization.
- `409`: Conflicts with the current state (duplicates, wrong lifecycle state).
- `422`: The request is well-formed but semantically invalid.
- `429`: Rate limit exceeded — retry after `Retry-After`.
- `500`: Internal server error.
- `503`: Transient error — retry with a narrower request.

## Changes

- **2026-11-03** `7c7a773b12ce`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/useboom/apis/boom-api/changes/api/v1/initiatives/:id/success-metrics/:rootId/delete.md)

---

[API](https://skmtc.dev/useboom/apis/boom-api.md) - [All operations](https://skmtc.dev/useboom/apis/boom-api/llms.txt) - [OpenAPI document](https://skmtc.dev/useboom/apis/boom-api/revisions/d596d92ed092?raw)