As we build our client-server applications in accordance with 2 most popular architecture approaches, SOA and Micro-services, we often build APIs to ensure communication between modules of the system. And it is usually REST API.
Building RESTful web services, like other programming skills is part art, part science. As the Internet industry progresses, creating a REST API becomes more concrete with emerging best practices. As RESTful web services don’t follow a prescribed standard except for HTTP, it’s important to build your RESTful API in accordance with industry best practices to ease development and increase client adoption. Presently, there aren’t a lot of REST API guides to help the lonely developer. RestApiTutorial.com is dedicated to tracking REST API best practices and making resources available to enable quick reference and self education for the development crafts-person. We’ll discuss both the art and science of creating REST Web services.
—Todd Fredrich, The REST API Tutor
API is a usual part of almost every system we build and we are normally follow the best practices, described in details in the following document (PDF). Please also check the API Design Cheat-sheet, to understand more of our considerations when designing APIs.
Part of our business is development and marketing of our own software suite #digitalharbour, that is essentially an enterprise digital transformation suite, primarily designed for banking and financial services. As a matter of fact, #digitalharbour is an excellent PSD2 compliance solution for every type of financial institution. Please check our detailed page on this subject and feel free to refer in case you still need PSD2-compliant API.