Move a page
Put a tab at a given place, counting from 1.
Every page of the version is numbered from 1 again afterwards, so the positions stay a run of whole numbers with no gaps. A place past the end puts the page last rather than being refused.
Parameters
Sent as JSON. Anything not listed here is ignored.
The id of the template. A path that is not a uuid answers 404 without a query being run, so neither the slug nor a sequential number reaches anything here.
The number of the version within its template, counting from 1, which is the number shown in the version history and the number a change note refers to. It is not a row id, so version 1 of one template and version 1 of another are different things reached through different templates.
The id of the page.
Where to put the page, counting from 1.
Returns
The page with the place it now holds.
The page.
Always structure_version_page. It names the kind of record, so a caller holding several kinds can tell them apart without looking at where they came from.
The id of this record, as a string even when it reads as a number. It is what every endpoint naming this record takes.
Everything the record holds.
How the page is addressed in a browser link. It is settled when the page is added and survives every rename.
What the tab says.
Where the tab sits, counting from 1.
The blocks placed on this page. Empty here, since these endpoints answer with the page itself rather than with what is on it. Read the version to get the whole structure.
Rate limit
Sixty requests per minute, per user, shared by every key and device. Every answer carries the budget left in X-RateLimit-Remaining.
Keys act as you, with exactly the access you have. Make one per integration so you can revoke it alone.