links
DELETE /v1/content/link-sets/{linkSetId}
Delete a link set no recipe is using.
Authentication
Send an API key as a bearer token. This endpoint does not state a specific permission in the specification, so give your key the least it needs and check the response rather than assuming.
This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X DELETE https://api.zinndigital.com/v1/content/link-sets/{linkSetId} \
-H "Authorization: Bearer zdk_live_…"Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
Gated on `links.edit`. Refused with `422` while any recipe still points at this set, and the refusal names those recipes. Deleting one out from under a recipe would leave it running, costing credits, and publishing articles with no links in them — so archiving is offered instead.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
linkSetId (path) | string | Yes | — |
Errors this endpoint can return
401 · 403 · 404 · 422