<p>Topics include:</p><ul><li>Does it make sense to scope resources to the authenticated user or should you always use sub-resources?</li><li>When to use nested resources and when to avoid them</li><li>Strategies for dealing with actions that don't seem to fit into REST</li><li>Breaking the mapping between your API and your database</li><li>Using singular sub-resources and optional fields to simplify your responses</li></ul><p>Links:</p><ul><li><a href="http://reinink.ca/">Jonathan's personal website</a></li><li><a href="http://platesphp.com/">Plates templating library</a></li><li><a href="http://glide.thephpleague.com/">Glide image manipulation library</a></li><li><a href="http://weblog.jamisbuck.org/2007/2/5/nesting-resources">Nesting resources</a> by Jamis Buck</li><li><a href="http://adamwathan.me/2014/04/12/theres-a-model-hiding-in-your-rest-api">There's a model hiding in your REST API</a></li><li><a href="https://apisyouwonthate.com/">Build APIs You Won't Hate</a> by Phil Sturgeon</li><li>Sponsored by <a href="https://laracasts.com">Laracasts</a></li></ul>

In this episode, Adam talks to Jonathan Reinink of Code Distillery about common API design challenges and how to fix them.

Full Stack Radio

35: Jonathan Reinink - Fixing Common API Design Mistakes