![[The AI Show Episode 151]: Anthropic CEO: AI Will Destroy 50% of Entry-Level Jobs, Veo 3’s Scary Lifelike Videos, Meta Aims to Fully Automate Ads & Perplexity’s Burning Cash](https://www.marketingaiinstitute.com/hubfs/ep%20151%20cover.png)
![Z buffer problem in a 2.5D engine similar to monument valley [closed]](https://i.sstatic.net/OlHwug81.jpg)
.png?width=1920&height=1920&fit=bounds&quality=70&format=jpg&auto=webp#)
_Kjetil_Kolbjornsrud_Alamy.jpg?width=1280&auto=webp&quality=80&disable=upscale#)
![Samsung teases Galaxy Z Fold 7 with an absolutely bizarre ‘Ultra experience’ [Video]](https://i0.wp.com/9to5google.com/wp-content/uploads/sites/4/2025/06/galaxy-z-fold-7-teaser-1.jpg?resize=1200%2C628&quality=82&strip=all&ssl=1)
![iPhone 18 Pro, iPhone Fold to Feature New A20 Chip With Advanced WMCM Packaging [Report]](https://www.iclarified.com/images/news/97494/97494/97494-1280.jpg)
POST / PUT with no explicit id in request
In the context of POST/PUT endpoints, is it ok to retrieve the id from the authentication token instead of forcing the user to send it via a path variable? For example, PUT /api/users that updates the logged-in user's info would arguably be more convenient for clients than PUT /api/users/{id}. Assuming, of course, the said token contains a userid claim. Another idea is to have a forwarding endpoint: PUT /api/users would forward to PUT /api/users/{id} passing the userid claim.
In the context of POST/PUT endpoints, is it ok to retrieve the id from the authentication token instead of forcing the user to send it via a path variable?
For example, PUT /api/users that updates the logged-in user's info would arguably be more convenient for clients than PUT /api/users/{id}. Assuming, of course, the said token contains a userid claim.
Another idea is to have a forwarding endpoint: PUT /api/users would forward to PUT /api/users/{id} passing the userid claim.
