# Delete a conversion goal

Source: https://kirora.io/docs/api/reference/deleteConversionGoal

`DELETE /v1/conversion-goals/{id}`

Requires an API key with the `conversion-goals:write` scope. [About keys and scopes](https://kirora.io/docs/api/reference/authentication)

Works with integration, agent and partner keys.

A repeat after success returns 404 or 409: treat that as done. [About idempotency](https://kirora.io/docs/api/reference/idempotency)

Removes the goal and the conversions recorded against it, for good. Refused with 409 `IN_USE` while it still decides something: a campaign's A/B test that picks its winner by conversions on this goal and has not picked one yet, or a live or paused journey with a conversion goal exit. `details.usedBy` names them (`campaigns`, `journeys`). In the dashboard, admins and owners only.

## Path parameters

- `id` (string, required, uuid) — The conversion goal's id.

## Header parameters

- `Kirora-Workspace` (string, optional, pattern `^[A-Za-z0-9._:-]{1,128}$`) — Partner keys only: the child workspace to act in, by the external id the partner gave it. Without it, a partner key acts in its own workspace. Any other key that sends it is refused with 403, and an unknown workspace is 404.

## Returns

Returns `204 No Content` with an empty body. It can also return `409 Conflict`; see the statuses below. Otherwise returns an error; [Errors](https://kirora.io/docs/api/reference/errors) lists every code and which to retry.

Statuses:

- `204 No Content`: Deleted.
- `409 Conflict`: The request conflicts with current state — a duplicate unique value, or a resource whose status does not allow this operation.

## Example

```bash
curl -X DELETE https://api.kirora.io/v1/conversion-goals/018f2a4e-6b1c-7d3e-9f40-37386ae05a6b \
  -H "Authorization: Bearer $KIRORA_API_KEY"
```