links
POST /v1/link-edits/{editId}/undo
Put back exactly what a bulk edit replaced.
Authentication
Send an API key as a bearer token. The endpoint checks links.edit; a key without it is refused with 403, not 404.
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 POST https://api.zinndigital.com/v1/link-edits/{editId}/undo \
-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
Reverses the items that actually applied — a stale item is not reversed, because re-inserting a link the customer had already removed themselves would be a change nobody asked for, and a failed item never wrote anything to put back. Once. A second undo would reverse the first and put the original change back, which is the opposite of what the button says, so it is a 409.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
editId (path) | string | Yes | The bulk edit's id. |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
id | string | Yes | — |
target_id | string | No | — |
target_host | string | Yes | The host as it read when the edit was made. Kept as a string as well as a key, because a rewrite can empty a target of its last link and an audit line reading "edited (deleted… |
action | string<rewrite, unlink> | Yes | — |
new_href | string | No | — |
new_text | string | No | New visible text. Empty means keep whatever each link already says — which is the common case, because one target's links carry many different anchors and flattening them all to… |
status | string<pending, running, applied, partial, failed> | Yes | partial is the honest answer when some sites succeeded and some did not, and it exists because the other two are lies in that case: an operator's next action depends entirely on… |
expected_links | integer | Yes | What the operator was told would change, recorded when they confirmed it rather than recomputed later. The whole value of a confirmation is that it can be held up against the… |
expected_posts | integer | Yes | — |
expected_sites | integer | Yes | — |
undo_of | string | No | The edit this one reverses, if any. |
undone_by | string | No | The edit that has already reversed this one. Present so the screen offers undo once — two undos of one edit put the original change back. |
created_at | string | Yes | — |
finished_at | string | No | — |
items | LinkEditItem[] | No | — |
Errors this endpoint can return
401 · 403 · 404 · 409 · 422 · 503