Question

Which of the following is not a best practice for designing an API?
a) using informative name
b) naming the endpoint
c) using api keys
d) not using a version number in the URL

Answer 1

Answer:

REST APIs are one of the most common kinds of web services available today. They allow various clients including browser apps to communicate with a server via the REST API. Therefore, it’s very important to design REST APIs properly so that we won’t run into problems down the road. We have to take into account security, performance, and ease of use for API consumers.

Otherwise, we create problems for clients that use our APIs, which isn’t pleasant and detracts people from using our API. If we don’t follow commonly accepted conventions, then we confuse the maintainers of the API and the clients that use them since it’s different from what everyone expects.

In this article, we’ll look at how to design REST APIs to be easy to understand for anyone consuming them, future-proof, and secure and fast since they serve data to clients that may be confidential.

Answer 2

Option C) using api keys

using api keys not a best practice for designing an API

• It is standard procedure for APIs to accept JSON queries as the payload and to return responses in JSON format. A standard and open format for data transport is JSON. Its ability to encode and decode JSON using the Fetch API or another HTTP client is a JavaScript-derived feature.
• An excellent API considers the developer's perspective and offers thorough, accurate, and understandable documentation. By considering typical use cases—the kinds of things a true API user will need—it also aids engineers.
• There are various others, but the most popular ones are GET, POST, PUT, and DELETE. There is no restriction on the number of methods that may be declared, which enables future ways to be specified without compromising the infrastructure that is already in place. Idempotence is a topic that applies to this subject.
• Apply APIs only in known, everyday use scenarios. Consider the complete API lifecycle in advance. Never make your APIs available for the public to use or licence.

#SPJ2