Integration is the action to search, modify or send information to a service. The integrations are divided into two:

• Native: The Weni platform can integrate with APIs that have REST/Json format through a Webhook card or through a pre-existing application in the Integrations menu.
• Non-native: We do non-native integrations for APIs that are not REST/Json. However, in this case, we must analyze the effort and scope of the request, since we use external services to consume and model the API, for example Back4app and Pipedream.

It is a form of communication between systems, in which one of them provides information and services that can be used by the other (Weni Platform). Typically an API has:

• URL
• Documentation explaining how it can be used
• Available endpoints/features
• Authentication forms to use the API, if necessary.

Webhook is a technology used to allow communication between two applications in real time. At Weni Platform we can search and even update information in other systems through the Call Webhook card.

To pass information to a system using API you must use the body of the request (body) or pass it directly in the URL (query). The API documentation will tell you how to do this.

In this image we can see the documentation of Weni's API:

In this image, we can see what the request body would look like to create a contact with a name and WhatsApp number.

Tip: The Call Webhook card allows the use of variables, such as @results, @contact, and @fields. Learn more about variables here.

The API documentation works as a manual that helps us understand how to integrate. It will inform you if the requests are in the native architecture of the Weni platform: REST/Json.

Note: If your API architecture is not REST/Json, it is still possible to integrate, but you will need to model this API.

To view the API return, access the Webhooks log in the Flows Module:

Have more questions about API? Share in our community 😉 We have an expert team to answer your questions.