Resource creation is made using POST requests on the collections. Identifiers for new resources are created in the back office.
If the client sends the same request twice (because of network failure, time out, or wrong user behaviour on the GUI, or any other reason) it will create two identical resources with a different identifier for each.
To avoid creating these duplicated resources when using POST, our interfaces implement unicity checks when parsing the input.
The check is performed on the disambiguatingToken field at the root path of the JSON payload.
•This field should be considered mandatory for API clients
•Clients of the API are supposed to value this property in a globally unique way (using Universally Unique Identifiers (UUIDs) is preferred).
•Implementing this practice in the client enforces idempotency of POST requests in case of resource creation.
