Unfortunately no, but some (many?) REST APIs turn the problem on its head by using private autoincrement IDs in the database and public UUIDs with either a dire

Unfortunately no, but some (many?) REST APIs turn the problem on its head by using private autoincrement IDs in the database and public UUIDs with either a direct 1:1 mapping between the two or a mapping that is unique to each user. This is mostly done for security reasons but I'm not sure if it's considered a best practice because it can introduce additional complexity at the sharding and caching levels (among others): https://softwareengineering.stackexchange.com/questions/371413/use-uuid-on-top-of-auto-increment-id https://softwareengineering.stackexchange.com/questions/3714... https://stackoverflow.com/questions/15360245/when-using-uuids-should-i-also-use-auto-increment https://stackoverflow.com/questions/15360245/when-using-uuid... https://softwareengineering.stackexchange.com/questions/139450/is-obscuring-obfuscating-public-facing-database-ids-really-a-best-practice https://softwareengineering.stackexchange.com/questions/1394... https://softwareengineering.stackexchange.com/questions/346971/should-backend-ids-be-public-or-not-on-a-rest-api https://softwareengineering.stackexchange.com/questions/3469...