Rotate approval link - YGO Client API

Replace one hotel's link token. The old token stops resolving immediately, so this is how a leaked or mis-sent link is invalidated. Everything else survives: the approval status, the approval timestamps and approver, the feedback history and the hotel's identified contacts, whose secrets keep working on the new token. Send the new link to the hotel afterwards — the old one is dead. A link that was revoked cannot be rotated back to life: it answers 404 Approval link not found, and createApprovalLinks is the way to mint a fresh one.

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Responses

🟢200

application/json

The link with its new token. The previous token no longer resolves.

Headers

Bodyapplication/json

🟠400rotateApprovalLink_BadRequest

🟠401rotateApprovalLink_Unauthorized

🟠403rotateApprovalLink_Forbidden

🟠404rotateApprovalLink_NotFound

🟠429rotateApprovalLink_TooManyRequests

🔴500rotateApprovalLink_InternalServerError

curl --location 'https://api.ygo.ai/v2/project/content/rotateApprovalLink' \ --header 'X-Project-ID: ' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "HotelID": "019d9c2e-0ef8-7458-b0fa-8bed7182eb30" }'

{ "Data": { "HotelID": "019d9c2e-0ef8-7458-b0fa-8bed7182eb30", "HotelName": "Sotavento Beach Club", "GiataID": 5721, "MasterCode": "FUED0009", "Token": "cP7tpTJPwR9mLxYaKu2NsE4vZbQdHfGjT1oIcXn6yA0", "TokenPreview": "cP7tpTJP...", "Status": "approved", "ApprovedAt": "2026-08-25T18:19:18.860882Z", "ApprovedTextGeneratedAt": "2026-08-19T14:14:57.674681Z", "ApprovedBy": { "Name": "Ayşe Yılmaz", "Email": "ayse@sotavento.example", "Phone": "+34 928 000 000" }, "LastOpenedAt": "2026-08-25T18:19:18.966928Z", "Created": false, "CreatedBy": "editor@example.com", "CreatedAt": "2026-08-25T18:19:17.522006Z", "UpdatedAt": "2026-08-25T18:19:18.860882Z" } }