API Digest #95: When the Right API Solution Is Not Always the Sensible One

Published 11 June 2018 | Updated 11 June 2018 |

API2Cart continues to deliver the most interesting news from the world of APIs via our digest. In today’s edition you will find a brief overview of the following articles:


1. Synthetic Monitoring vs. API Monitoring: Why You Need Both

Synthetic monitoring and API monitoring are two types of monitoring that can seem similar, but are actually quite different. Chris Riley defines what they have in common, how differ, and which types of use cases each supports.

Read the article


2. When The Right API Solution Is Not Always The Sensible One

In the article Kin Lane is discussing the proper way to design APIs and the reasons why we still see just as many poorly designed APIs in 2018. It is because the best design doesn’t always win. Sometimes you just need the right design for the job, and the one that will make sense to the audience who will be consuming it.

Read the article


3. Five Things You Need to Know About API Security

 Every web and mobile application out there is powered by APIs. As an application architect, you cannot overlook design time or operational protection of APIs. In the article, you will find five things you need to know about the API security in order to protect your applications.

Read the article


4. What is WebSub? Common Cases and Implementations

In the article Kristopher Sandoval defines that WebSub is a promising technology providing quite a bit of value. Notification of new content, be it new codebase revisions or new job postings, is the principal function of many APIs, and as such, simplifying this process and reducing demanded resources can be hugely beneficial for most APIs that fit into the given criteria.

Read the article


5. 4 Stakeholders of API

There are four main groups of stakeholders: API providers, API customers, API consumers, and end-users. In this article Amancio Bouza describes each group, their competencies, as well as their interests.

Read the article


6. Best practices for deprecating APIs

If you have been working on developing and maintaining APIs, you might have been familiar with the problem of having to maintain multiple versions of an API. It is important to let the consumers know that a particular version of your API is deprecated. Sumanth N.S. points out two approaches concerning the use of warning header in the response of your API with an explicit message explaining the deprecation.

Read the article


If you are interested in getting the latest news in the API world, check our digest #94 and #93 as well as stay tuned for the new blog posts.

In case you are interested in unified shopping cart API, your best choice is API2Cart. Click the button below and schedule a call with our expert.