List template versions
List the versions of one template, newest first.
Every change to a structure produces a version rather than editing one, so this is the whole history of the template and the record of what was frozen when. A published version never changes again, which is what lets a record made a year ago go on rendering exactly as it did.
At most one version is a draft at a time. Publishing a later version does not change an earlier one, so several versions read as published and the template says which one is current. Each keeps its record_count for as long as anything is still on it.
This answers with the versions and not with what they contain. Read one version to get its pages, its sections and its fields.
This endpoint also answers QUERY, with the same parameters sent in the request body. How QUERY works.
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.
Which page to answer with.
How many one page holds, between 1 and 100. A number outside the range is brought back into it rather than refused.
Returns
A page of version objects, newest first, and how many there are in all. A template belonging to somebody else answers 404.
The versions on this page. An empty list rather than an error when there are none.
One version.
Always structure_version. 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.
Which version this is within its template, counting from 1. It is what the address of this version takes, and what a change note refers to.
Either draft or published. A draft is still being designed and may be changed freely. A published version is frozen and never changes again, and stays published after a later version replaces it, so read published_version_number on the template to know which one a new record is put on.
What changed since the version before, written when this one was published, or null on a draft and on the first version of a template. It is what somebody deciding whether to move their records reads.
When the version was frozen, as a count of seconds, or null while it is a draft.
Always null. Publishing a later version does not retire the one it replaces, because the records still on it go on working exactly as they did.
How many records point at this precise version. A record follows the version it was put on until somebody moves it deliberately, so a retired version keeps a count above zero for as long as anything is still on it.
The number of the version this one was started from, or null on the first version of a template.
When the version was started, as a count of seconds.
When it last changed, as a count of seconds. Equal to created_at until it first changes. A published version never changes, so this stops moving at publication.
Where to find this record.
The absolute address this record is read from.
Where you are in the collection.
The page this is, counting from 1.
How many one page holds, which is the size that was asked for once it has been brought into the allowed range.
How many versions there are in all, not how many are on this page.
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.