The API space is ever-evolving. As the needs of end-users grow in both complexity and frequency, new software development strategies continue to emerge. When working with APIs, it’s not uncommon to see a network of systems handling a single purpose. In fact, during the modern age of microservice architectures, this has become the design paradigm de jure, with each API operating a small fraction of the much larger machine. Read more
There are nearly as many options for API tools and design styles as there are APIs themselves. The modern API industry has a variety of specifications, frameworks, paradigms, architectures, integrations, and extensions that make each API instance unique. Today, we’re going to take a look at three of those options. Read more
API concepts, especially those around security, can often be confusing. While we generally understand basic concepts like “credentials,” trying to explain how the ROPC Flow differs from the Client Credentials Flow can often devolve relatively quickly into acronyms and diagrams. Accordingly, we’ve compiled a list of 20 resources that help to nail these concepts down. Read more
The world of APIs is often one of competing standards, interests, and solutions. While we tend to talk about the API space as a cohesive community, the reality is that APIs on the internet encompasses something more universal.
In the API documentation space, this ultimately comes down to a question of consumption. Read more
The life of an API follows a predictable lifecycle – from creation to deprecation, each stage of the API lifecycle denotes an important event, and it carries with it a set of best practices. API developers tend to think about the future in very positive ways – how the API will behave, what its design will be – but in doing so, they don’t always consider what the end of that API might look like. Read more
