Restore a deleted catalog entry
POST/v1/catalog/entities/{entityId}/restore
Brings back a deleted catalog entry, as Show deleted → Restore does — and every deleted parent above it, so it reappears in the tree. Another live entry holding its Google place meanwhile is a 409 place_taken. Undo with POST /changes/{changeId}/revert (deletes them again).
Permissions: catalog:write · Kind: write · Cost: 1 unit · MCP tool restore_catalog_entity
Undoable: the response carries Bymundi-Change-Id; revert it with POST /v1/changes/{changeId}/revert.
Path parameters
| Field | Type | Required | Description |
|---|---|---|---|
entityId |
uuid | yes |
Body
None.
Response 200
| Field | Type | Required | Description |
|---|---|---|---|
object |
"catalog_entity" | yes | |
id |
uuid | yes | |
kind |
"destino" | "punto" | "alojamiento" | "actividad" | "servicio" | yes | |
name |
string | yes | |
placeId |
string | yes | |
cityKey |
string | yes | |
externalId |
string | yes | |
place |
object | yes | |
images |
object[] | yes | |
tags |
string[] | yes | |
origin |
"human" | "ai" | "api" | "import" | yes | |
content |
object | yes | |
updatedAt |
string | yes | |
deletedAt |
string | null | yes | |
restoredIds |
uuid[] | yes |
Errors
Errors are problem details. Besides the refusals described above, any call like this one can return:
invalid_request— Invalid requestunauthorized— Missing or invalid API keyinsufficient_scope— Missing permissionrate_limited— Rate limit reachednot_found— Not foundidempotency_key_reused— Idempotency-Key reusedrequest_in_progress— Request in progress