Best Practices

To become the best coder on the Earh, you should know the best practices. There is not a silver bullet and people love to argue about the best practices. We have created this section to find all possible arguments for each best practice and to find all pros and cons, so you can find them easily whenever you need them.

Do you know any best practices we are missing? Please, put them to the comments, so we can add them to the database and start discussing them with you and the rest of the world.

• Become a Best practice hero.
  Help us to grow the catalogue of best practices.
  Submit a best practice

Recently added best practices

• Use query string to filter resource collections
• Never use CRUD function names in URIs
• Do not use underscores in URIs
• Do not use file extensions in API endpoint URIs
• Use lowercase letters in URIs
• Do not use forward trailing slash in URLs
• Use the right terminology
• Use consistent patterns across all API endpoints
• Do not return plain text
• Use SSL to protect your data during transfer
• Your API should be stateless
• Do not use session in your RESTful API endpoints
• Do not trust the input parameters
• Use correct HTTP status codes
• Use HTTP headers for content negotiation
• Use sub-resources for relations
• GET should never change the state
• Use plural nouns
• Use correct HTTP methods
• Use nouns, not verbs