The driver in this article is not to start a discussion about what things need technical ability to understand compared to the logical components of a highly scalable SaaS-based platform. We are going to help you fit a complex system into a logical block in a way that the layman understands
Let’s take an example where you talk to a friend. If you two speak the same language, it is easy for one to understand what the other is saying
ImagineBut Imagine talking to the same person who doesn’t speak the language. That looks awkward, right?
Swap people in these images with the systems. APIs can be considered as a communication tool throughout the system. Let’s take an example. You have two systems; System A is Engati and System B is the ticket system. Suppose you want to create a ticket using system B through Engat. To achieve this, both systems must communicate in one language; They must adhere to one API standard.
Now you need to think about whether there are different languages to communicate between these systems. Of course it is. Like English, French, Italian, and Hindi, there are several ways to communicate, such as HTTP REST, SOAP, GraphQL, Sockets, etc. And just like English is the language most people try to speak to communicate globally, systems often support REST API-based communication ( again, there are always a bunch of people who don’t want to speak English)!
Just as all languages have grammar, syntax, instructions, and prohibitions, communication between systems has its own rules. Let’s look at the details of the speech / grammar equivalence of the REST API.
To go back to the example where Engati tried to create a ticket for the ticket system, it is a creation operation. Therefore, Engat must use the REST API in the ticketing system. To invoke the API, you need to know the parts of speech / grammar matching, i.e. URL, Parameters, Request Type (which should preferably be POST), Request Body.
Like, when you use a language dictionary to understand language words, we need to look at the system documentation to understand the request and response format. What details are sent and what is received are more specific to each system we are talking to.
The next time you’re looking for integration between two systems, keep in mind that APIs are just two people (systems) talking to each other under all technical layers.
Engatin wide documentation page allows you to browse APIs and create extensive functionality around the platform.
This article was originally published In Engati blogs.