Chapter 4. Consuming APIs
Up to this point, we’ve discussed why APIs are important, how to model them, and how to implement the code behind them. In this chapter and the next, we’ll discuss how to best consume APIs.
Identify Clients
Broadly, your clients can fall into one of the following three categories:
- Internal applications
-
Internal microservices that rely on functionality exposed by your APIs
- Digital Experience Platforms
-
Platforms that allow non-technical and semi-technical business users to build experiences for different customers. Grew out of web content management space
- Custom frontends
-
Custom web UIs, native mobile, embedded devices, social media, etc.
These three categories of clients have different requirements that will change how you model, build, and consume APIs.
Start by building an inventory of all known clients. If you have an existing API that you’re replacing, trace the source of all the inbound API calls. Your existing API may have clients you never knew about.
Then, imagine what kinds of clients you’ll see more of. If you’re selling consumer packaged goods, many of your future clients will probably be Internet of Things (IoT) devices, like smart refrigerators. If you’re selling apparel, many of your future clients will probably be magic mirrors and similar devices.
Finally, look at the characteristics and capabilities of each type of client:
- Language
-
What type of language can be used to consume the APIs? Does it have to be plain REST, or can you ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access