Best Practices for Designing a Pragmatic RESTful API
What formats should you accept? How should you authenticate? Should your API be versioned?
api naming-conventions endpoints endpoint-design tutorial article

Your data model has started to stabilize and you're in a position to create a public API for your web app. You realize it's hard to make significant changes to your API once it's released and want to get as much right as possible up front. Now, the internet has no shortage on opinions on API design. But, since there's no one widely adopted standard that works in all cases, you're left with a bunch of choices: What formats should you accept? How should you authenticate? Should your API be versioned?

Don't forget to tag @vinaysahni in your comment, otherwise they may not be notified.

Authors community post
Share this project
Similar projects
Flask
The Python micro framework for building web applications.
NSFW Image Classification REST API built with TensorFlow.JS
A ready-to-use & open-source NSFW Image Classification REST API built with TensorFlow.JS and NSFW.JS for effortless Content Moderation
OpenAI API
API for accessing new AI models developed by OpenAI.
Geocoding in Python Using Google Maps API
The article will focus on geocoding in Python which is getting coordinates for an address or any place around the world and calculating distances between ...
Top collections