Revoke Event Share Link
Kill one clip link. The recipient's next load is the same 404 an unknown token gets.
IDEMPOTENT: an already-revoked link answers 200 with the UNCHANGED first revoker and first timestamp. A second revoke must not rewrite the audit, and a client retrying a click must not see an error for a link that is already dead.
A link id belonging to ANOTHER event is the same 404 as one that does not exist — this route must not confirm the existence of link ids outside the event the caller can already reach.
A FAILED SEND DOES NOT AUTO-REVOKE ITS LINK, and this route is why. A provider failure is often AMBIGUOUS (the network died; Surge may well have sent it), so the customer may already hold the URL and revoking would break a message that did arrive. The operator sees the failed row with its link and decides.
Request
- Base URLhttps://api.verdun.ai (the document declares no server; this is the origin it was published from)
- URLhttps://api.verdun.ai/events/{event_id}/share-links/{link_id}/revoke
- AuthHTTP bearer
Path parameters
Response
Successful Response
Changes
No recorded changes to this operation across all 2 revisions of this API.