Updates and Conflict Prevention

All Management APIs use the same pattern for conflict prevention when updating resources.

When updating an existing resource, you must include the entire resource, including all its existing unchanged properties. It's not possible to update only a subset of properties.

Additionally, you must specify the resource's current version using the X-Resource-Version HTTP header. This version is compared with the current version to prevent a client from overwriting a resource that has been updated since the specified version was retrieved. If the version doesn't match, the update will be rejected.

To prevent any unexpected changes or conflicts, always update resources in the following order:

  1. Fetch the current resource along with its current version number.
  2. Make any desired changes to the resource data by editing the response object.
  3. Update the resource by passing the changed resource object along with its current version number.