The European financial services industry is on the cusp of a technological revolution. Reforms like PSD2 and the CMA initiative in the UK are forcing traditional banking institutions to enter the API Economy as active participants.
Great news for the FinTech scene, one would think; at last the banking platforms are being opened up ready for third-parties to securely access a customer’s data without the need to screen scrape online banking interfaces (also frequently referred to as ‘direct access’). Read more
Error codes are almost the last thing that you want to see in an API response. Generally speaking, it means one of two things — something was so wrong in your request or your handling that the API simply couldn’t parse the passed data, or the API itself has so many problems that even the most well-formed request is going to fail. Read more
If you have arrived at the Nordic APIs blog there is good chance you have some inkling of what an API is and why you might need one. However, for the uninitiated, APIs (Application Programming Interfaces) and especially the API economy can be a confusing and fragmented space with some loose standards, an incredible amount of diversity, and a seemingly impenetrable barrier of technical jargon. Read more
We’ve discussed GraphQL at length previously – and while the discussions on how GraphQL works are obviously very powerful, we’ve yet to dive into some of the best practices that should be adopted when developing a GraphQL-centric API.
Today, we’re going to do exactly that. Read more
The microservices design paradigm has become a prominent software design methodology now that API-first industries embrace a more decoupled operational strata. In the past we’ve discussed asynchronous choreography, BFF design, as well as identity control for microservices. However, one question remains: what is the most effective means for testing microservices? Read more