Remove a field
Take a field out of a section.
The values already written under the field are not destroyed. They are detached and kept, so nothing a person typed disappears because somebody changed a structure, and a field put back finds them again.
As with the other two, a published section is drafted first and the published one is left alone.
Path 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.
Returns
Nothing. A field of a template belonging to somebody else answers 404.
Rate limit
Sixty requests per minute, per user, shared by every key and device. Every answer carries the budget left in X-RateLimit-Remaining.
No content.
Keys act as you, with exactly the access you have. Make one per integration so you can revoke it alone.