List a collection field's change history
GET /collections/{id}/fields/{field_id}/history
Returns the recorded changes to one field’s value on one collection,
newest first: the old and new value, when the change was made, by
whom and its set_by. Any signed-in user can call this. It doesn’t
check the field’s read_capability, whether you may see the
collection, or whether it exists.
limit defaults to 50, but here it isn’t clamped: the 1-500 range
shown isn’t enforced. 0 returns nothing, a value above 500 allows
more entries when there are more, and a negative value within the
32-bit range is an error. Values beyond the 32-bit integer range
wrap around when converted, so they can become 0, a negative number
or a different positive one. There is no paging, and entries
recorded at the same time have no fixed order. Entries come from
these routes and from vocabulary merges, and they are deleted with
the collection or field when either is removed for good.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The collection’s id.
The field definition’s id.
Query Parameters
Section titled “Query Parameters ”Maximum number of entries to return. This route doesn’t clamp it: 0 returns nothing, a negative value within the 32-bit range is an error, and values beyond that range wrap around.
Responses
Section titled “ Responses ”Recorded changes, newest first.
object
The history entry’s id.
The collection’s id.
The field definition’s id.
The value before the change, as an object holding the field’s type and the value. Left out for a first write.
object
The value after the change, in the same form. Left out when the value was removed.
object
When the change was recorded.
The account that made the change, if known.
The set_by of the write that made the change; manual for a removal through this API and computed for a vocabulary merge.
Authentication required, missing, or invalid
object
Human-readable error summary
Example
the request could not be completedExample
{ "error": "authentication required: sign in and retry with a valid session or API token"}Resource not found
object
Human-readable error summary
Example
the request could not be completed