---
title: "Delete a conversion destination"
method: DELETE
path: "/v1/accounts/{accountId}/conversion-destinations/{destinationId}"
tags: ["Conversions"]
---

# Delete a conversion destination

`DELETE /v1/accounts/{accountId}/conversion-destinations/{destinationId}`

LinkedIn-only today. LinkedIn does not expose hard-delete on conversion
rules — what their UI calls "delete" is the same `enabled: false` flip
we apply here. The rule remains fetchable via GET with
`status: 'inactive'`; the unified discovery endpoint hides it by
default.

`adAccountId` may be passed as a query parameter (recommended) or as
a JSON body field for clients that can send DELETE bodies.

## Path parameters

- `accountId` string, required
- `destinationId` string, required

## Query parameters

- `adAccountId` string

## Response `204`

Soft-deleted.

## Other responses

- `400` — adAccountId missing, or accountId is not a valid id.
- `401` — Unauthorized
- `403` — Ads add-on or LinkedIn reconnect required.
- `404` — Account or destination not found.
- `405` — Platform does not support deleting destinations.
- `429` — LinkedIn rate limit hit. Retry with backoff.

---

[API](https://skmtc.net/zernio/apis/zernio-api.md) · [All operations](https://skmtc.net/zernio/apis/zernio-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/zernio/zernio-api/revisions/1e9a379eafca/schema)