ETags are returned on all GET that return a single record as well as all PUT and POST requests. The system will respect ETags for GETS, PUTS, and DELETES.
For example, if a GET on a single work order is issued and it includes a header with the following:
If-None-Match: "686897696a7c876b7e"
The Lucity REST API will check the version of the work order in the database, if it matches the version provided in this ETAG, the Lucity REST API will return a 304 NOT MODIFIED.
For Updates, ETAGS can be used to make sure that one user does not overwrite another user’s data. If, on a PUT, the following is included on the header:
If-Match: "686897696a7c876b7e"
The Lucity REST API will only make the requested update if the version of the record in the database matches the provided ETAG.