Think you know your target audience? As diversity increases in the API economy, we reconsider API user segmentation, defining specific traits that make up today’s unique API consumer.| Nordic APIs
To kick off a series of blog posts on the API lifecycle, we’ll define what we mean by this term and explore it from a high level. In subsequent posts we’ll dig into the details, so be on the lookout for those!| Nordic APIs
In this article we offer both practical tips on technical implementation, and more philosophical considerations on complexity when designing an API.| Nordic APIs
Continuous versioning replaces typical URI versioning (v1, v2, etc) to withhold the server to client bond, equating to consistency and better API agility.| Nordic APIs
Why would a Public API be retired? What business decisions make up a deprecation? This aticle analyzes recent public API retirements as examples to find answers to these tough questions| Nordic APIs
Far different than traditional software versioning, API versioning can have complex implications for the products using it downstream. In this article we cover the most widely used approaches in the API space, including traditional URI versioning, using the Accept Header, continuous versioning, and more.| Nordic APIs
We compare two ways to update a web API – revisions are incremental, non-breaking changes to an API, whereas versions are often-breaking, major changes.| Nordic APIs
