Concurrency handling
The API implements optimistic concurrency control for PUT
and DELETE
operations to prevent conflicting updates to resources.
How It Works
Getting the Concurrency Token
- Send a
GET
request to the resource endpoint - Retrieve the
RowVersion
property from the response
Using the Concurrency Token
Include the RowVersion
in the If-Match
HTTP header when performing:
- PUT operations (updates)
- DELETE operations
Error Handling
Important: The API validates the concurrency token before processing the request:
- If the token matches: The operation proceeds
- If the token doesn't match: The operation doesn't proceed and returns HTTP
409 - Unauthorized
, indicating the resource has been modified
This prevents unintended overwrites of changes made by other clients.
Updated 3 months ago
What’s Next