So much has been said about APIs… APIs to send SMS and WhatsApp messages, to consume data, to integrate systems… APIs in sites, publishing APIs, and consuming APIs. Then comes the new GeneXus API object and we wonder… what is the new object for? Who is it intended for? How is it used? What is there today and what lies ahead.
The API (Application Programming Interface) object defines an application programming interface of a group of programs, such as Procedures and Data Providers. An API then represents the ability to communicate between different software components and today is a key element for the architecture of all types of systems.
APIs are essential to make designing service-based applications easier and better organized. When modelling an API, it is important to be able to model an API mediation layer, which clearly separates the interface from the implementation and facilitates the incremental development and management of the evolution of an API.
Impact on an ecosystem: when an organization decides to single-handedly unblock its systems, processes and/or data by publishing an API, it is actually creating value and a potential source of income for both itself and its business partners. This generates a multiplier effect that yields an ecosystem known as API Economy, where an API is the basis for creating value. In addition to operating independently, APIs also enable the creation of new and unique apps, based on the combination of several APIs.
From a technical standpoint, we could say that an API object can group several services functionally related to one another. For each service, it declares an assignment between the internal name (exposed as a service) and the internal implementation in the KB. It provides flexibility in terms of service declaration, which allows setting the access route and other configuration details (HTTP method). It also allows indicating the name and type of the parameters, and offers a significantly flexible parameter transformation.
Detailed information on how to declare services and protocols –including an example– can be found in the technical article titled API Object, in the GeneXus Community Wiki.
4 Essential Talks for Technology Integration with GeneXus APIs
These three talks given at the latest GeneXus Meeting are recommended for an in-depth look at the API ecosystem. GeneXus offers a variety of tools for exposing the APIs of systems built with GeneXus, and the possibility of integration with any third-party system. It is important to keep this in mind so as to be ready when opportunities arise.
Builders in the API Economy
At present, every development requires some type of integration, as we live in the age of the API Economy. This year, the growth of APIs has been greater than the previous ones. What are the opportunities available and how can we leverage them with GeneXus? By Eugenio García, GeneXus Product Manager.
Tools to Showcase your Business
Alejandro Panizza, a member of the GeneXus R + D team, discusses the common problems that may be solved with APIs and also talks about service management.
Panel on Interoperability and Integration: Challenges and Experiences in the Age of APIs
In this panel, we can see different clients and aspects of the API world in action and their interaction with some examples of integration in various markets: from the standpoint of an ERP, Electronic Government and integration between all State agencies, Banking and Foreign Trade Software.