Confirm an edit request and apply it
For a domain proof, this re-fetches every affected site and checks the token before writing anything. For an email proof the same thing happens when the recipient opens the mailed link and presses the confirm button (the link itself only displays the pending change — mail scanners fetch links, and the token is single use), so calling this endpoint by hand is only needed if you kept the token.
On success: the change is written, every field is logged with its old value, the registered address is emailed an undo link valid 7 days, and a URL change resets the badge to unverified.
A metadata refresh takes two calls here. The first returns applied: false, status: "preview", the proposed changed values and an apply digest, and writes NOTHING — do not read a 200 as "done", check applied. Send the digest back as apply to save it. The page is re-read on apply and the digest re-checked, so if it changed in between you get a fresh preview instead of a write nobody saw. URL and email changes stay one-step: those values came from you and are not re-read.
Request
- Base URL: https://curlship.com
- URL: https://curlship.com/api/edit-confirm
- Auth: none declared
Request body
Example request
{
"request_id": 7
}Response
Applied, OR — for a metadata refresh sent without a matching apply digest — a preview that wrote nothing. Check applied.
Example response
{
"ok": true,
"listing": {
"id": 2076,
"url": "https://yourapp.com/",
"title": "YourApp — ship faster",
"created_at": "2026-10-12T09:04:05Z"
}
}Changes
No recorded changes to this operation across all 1 revision of this API.