RestorePageAPI mirrors the erdo_restore_page MCP tool.
The path is /v1/pages/restore/:pageID rather than /v1/pages/:pageID/restore because Encore forbids a parameterized segment (:pageID) at the same position as the existing static /v1/pages/validate route under POST. A static “restore” sibling to “validate” sidesteps that; delete stays RESTful (DELETE /v1/pages/:pageID) since DELETE has no static sibling at that position.
Authorizations
An Erdo API key (erdo_api_...) or scoped token (erdo_token_...).
Path Parameters
Response
Success response
share link and is only present while the page is public. Use these values verbatim — hosts differ across prod/staging/local.
action callers can reference it without importing the validator implementation.
successful content deploy/update). The page exists and is usable; the calling agent should surface this to the user and retry the failing op.

