The etag known to the client for the expected state of the unit. This is
used with state-changing methods to prevent accidental overwrites when
multiple user agents might be acting in parallel on the same resource.
An etag wildcard provide optimistic concurrency based on the expected
existence of the unit. The Any wildcard () requires that the resource
must already exists, and the Not Any wildcard (!) requires that it must
not.
The etag known to the client for the expected state of the unit. This is
used with state-changing methods to prevent accidental overwrites when
multiple user agents might be acting in parallel on the same resource.
An etag wildcard provide optimistic concurrency based on the expected
existence of the unit. The Any wildcard () requires that the resource
must already exists, and the Not Any wildcard (!) requires that it must
not.
An optional request ID to identify requests. Specify a unique request ID
so that if you must retry your request, the server will know to ignore
the request if it has already been completed. The server will guarantee
that for at least 60 minutes since the first request.
For example, consider a situation where you make an initial request and the
request times out. If you make the request again with the same request
ID, the server can check if original operation with the same request ID
was received, and if so, will ignore the second request. This prevents
clients from accidentally creating duplicate commitments.
The request ID must be a valid UUID with the exception that zero UUID is
not supported (00000000-0000-0000-0000-000000000000).
An optional request ID to identify requests. Specify a unique request ID
so that if you must retry your request, the server will know to ignore
the request if it has already been completed. The server will guarantee
that for at least 60 minutes since the first request.
For example, consider a situation where you make an initial request and the
request times out. If you make the request again with the same request
ID, the server can check if original operation with the same request ID
was received, and if so, will ignore the second request. This prevents
clients from accidentally creating duplicate commitments.
The request ID must be a valid UUID with the exception that zero UUID is
not supported (00000000-0000-0000-0000-000000000000).
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-16 UTC."],[],[]]