Move a field
Put a field at a given place in its section, counting from 1.
Every field of the section is numbered from 1 again afterwards, and a place past the end lands last. A published section is drafted first, exactly as it is for the other changes to a field.
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 placement, which is not the id of the section. It is the id a placement comes back with when a version is read.
The id of the field. It changes the first time a published section is changed, because the change opens a draft of the section and the fields are copied into it. The key does not change, and the answer carries the new id.
Where to put the field in its section, counting from 1.
Returns
The field with the place it now holds.
The field.
Always field. 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 field is named in an import or an export, settled when the field is added.
What kind of thing the field holds: one of text, textarea, number, boolean, url, email, phone, select, multiselect, radio, date, recurring_date, duration (a whole number of minutes), relation, file, image, avatar, address, repeater, divider, heading or help. The last three carry no value and are there to lay the form out.
What the field is called on the form.
A sentence shown under the field, or null when there is none.
What the empty box shows as an example, or null.
Where the field sits in its section, counting from 1.
Whether the record refuses to save without it.
Whether the value is hidden until somebody asks to see it.
Whether the value is repeated at the top of the record.
Whether two records of this template may hold the same value.
Whether two records sharing this value are likely the same record, so the pair is proposed as a duplicate. Not the same as unique: a household can legitimately share one telephone number, and proposing a pair is right where refusing the value would be wrong.
Whether the field holds several values rather than one. It follows from the type and is settled when the field is added.
The fewest repetitions allowed, or null when there is no floor.
The most repetitions allowed, or null when there is no ceiling.
How several values are ordered against each other, or null when the field holds one.
Settings belonging to this kind of field alone, or null. What it holds depends on the type.
Extra rules a value has to satisfy, or null.
What the field starts filled with, or null.
What a relation field points at, or null when the field is not a relation. It is settled when the field is added.
When the field was added, as a count of seconds since 1970.
When it last changed, as a count of seconds, or null.
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.