WHAT ARE THE REST API naming conventions?
Below, we’ll go over 7 tips for naming REST API endpoints that you should follow.
- Use nouns for naming URIs.
- Use intuitive, clear, unabridged names.
- Use forward slashes to denote URI hierarchy.
- Separate words with hyphens.
- Use lowercase letters.
- Avoid special characters.
- Avoid file extensions.
What would you validate when testing an API request?
For each API request, the test would need to take the following actions:
- Verify correct HTTP status code.
- Verify response payload.
- Verify response headers.
- Verify correct application state.
- Verify basic performance sanity.
Do you need validation in the REST API?
Again, the entire object would need validated in your PUT. It is great to have the validation in the REST API. You need a validation anyway and wy not to use it on the client side.
How can we protect our REST API applications?
This time I would like to describe how we can protect our REST API applications from requests containing invalid data (data validation process). However, validation of our requests is not enough, unfortunately. In addition to validation, it is our responsibility to return the relevant messages and statuses to our API clients.
What can a 303 status code do for a REST API?
Generally speaking, the 303 status code allows a REST API to send a reference to a resource without forcing the client to download its state. Instead, the client may send a GET request to the value of the Location header.
How is a document represented in the REST API?
In REST, you can view it as a single resource inside resource collection. A document’s state representation typically includes both fields with values and links to other related resources. Use “singular” name to denote document resource archetype.