Which workspace a page is in, for a link that names no workspace
For an old link (`/notes/p/<id>`, an email from before workspace URLs), so the app can send the tab to `/notes/w/<slug>/p/<id>`. It works across the caller's workspaces: the token may be for any of them. It answers only when Notes would let the caller read the page in its own workspace: they are a member with a product seat, Notes is on there, and they can see the page's space. Archived pages are located too, as the trash opens them. Every other case gets the same 404, byte for byte: no such page, someone else's page, a space the caller can't see, Notes turned off there, a malformed id, or a request made with an API key or an OAuth grant (those are bound to one workspace by consent). Both answers are `Cache-Control: no-store`. Rate-limited per user and per client IP (the edge's CF-Connecting-IP).
View as MarkdownAuthorization
bearer In: header
Path Parameters
uuidResponse Body
application/json
application/json
application/json
curl -X GET "https://example.com/v1/pages/497f6eca-6276-4993-bfeb-53cbbbba6f08/locate"{ "workspace_id": "0967198e-ec7b-4c6b-b4d3-f71244cadbe9", "slug": "string"}Save the rich document (optimistic concurrency)
Saves the doc with the revision the client loaded. A rev mismatch returns 409 with the current server doc so the editor can merge instead of clobbering another writer. Optionally syncs outgoing wiki-link edges in the same save. A tool publishing from an outside source also sends publishedRev, the rev its last publish wrote (easerix#461). If the page has moved past it, people edited it in Notes since, and the save is refused with 409 code edited_since_publish unless force is true. A save that carries publishedRev or force is recorded as a publish (publishedRev/publishedAt on the page). Ordinary saves omit both and are unaffected.
List a workspace's templates
Next Page