It’s not uncommon. Google AIP spec requires it for example. I think the main driver for it is implicit idempotency.
The client’s ID for a resource and the server’s ID for that resource need not be the same.
Of course, adding two IDs for a resource complicates things. But so too does trusting client-generated IDs to be universally unique.
alt Hacker News
The client’s ID for a resource and the server’s ID for that resource need not be the same.
Of course, adding two IDs for a resource complicates things. But so too does trusting client-generated IDs to be universally unique.