Evolution API Evolution API began as a WhatsApp controller API based on CodeChat, which in turn implemented the Baileys library. While originally focused on WhatsApp, Evolution API has grown into a comprehensive platform supporting multiple messaging services and integrations. We continue to acknowledge CodeChat for laying the groundwork. Today, Evolution API is not limited to WhatsApp. It integrates with various platforms such as Typebot, Chatwoot, Dify, and OpenAI, offering a broad array of functionalities beyond messaging. Evolution API supports both the Baileys-based WhatsApp API and the official WhatsApp Business API, with upcoming support for Instagram and Messenger.
Go to file
Guilherme Gomes cb76381466 refactor: reorder parameters and simplify EvolutionBot DTO
This commit refines the EvolutionBot integration by reordering constructor parameters for consistency and removing unused properties from the EvolutionBotDto and EvolutionBotSettingDto classes. Key changes include:
- Adjusted the parameter order in the EvolutionBotService constructor for improved clarity.
- Streamlined the EvolutionBotDto and EvolutionBotSettingDto by eliminating unnecessary fields.

These updates enhance the maintainability and readability of the EvolutionBot integration.
2025-05-27 17:52:45 -03:00
.github fix: added cache to identify duplicated messages on events 2025-02-03 15:37:11 -03:00
.vscode reversed settings 2024-09-11 22:00:57 +00:00
Docker merging with develop 2025-03-28 10:36:34 -03:00
Extras/chatwoot chore: adjusts in docker files 2024-08-09 07:17:09 -03:00
manager/dist refactor: update asset references in index.html and replace CSS/JS files 2025-05-27 17:37:01 -03:00
prisma Merge pull request #1456 from thiagoomatheus/main 2025-05-16 13:38:30 -03:00
public/images remove o arquivo 2024-10-24 08:52:56 -03:00
src refactor: reorder parameters and simplify EvolutionBot DTO 2025-05-27 17:52:45 -03:00
.dockerignore feat: updates api evolution for docker 2024-12-27 10:40:04 -03:00
.DS_Store git actions v2 2024-06-09 16:15:44 -03:00
.env.example Merge pull request #1498 from thrsouza/main 2025-05-25 11:10:40 -03:00
.eslintignore init project evolution api 2023-06-09 07:48:59 -03:00
.eslintrc.js Update ESLint configuration, Dockerfile, and package dependencies; add GitHub Actions workflow for code quality checks 2025-01-09 17:04:33 -03:00
.gitignore fix: improve message deduplication and edited message handling in Baileys service 2025-02-03 17:19:07 -03:00
.prettierrc.js wip 2023-07-26 11:12:00 -03:00
CHANGELOG.md changelog v2.3.0 2025-05-15 18:49:35 -03:00
docker-compose.dev.yaml removed docker-compose version as long it is obsolete 2024-09-11 22:18:30 +00:00
docker-compose.yaml lint changes 2025-03-28 10:58:32 -03:00
Dockerfile changelog v2.3.0 2025-05-15 18:49:35 -03:00
LICENSE fix: added cache to identify duplicated messages on events 2025-02-03 15:37:11 -03:00
local_install.sh feat: sh local install 2024-11-02 08:12:30 -03:00
package-lock.json changelog v2.3.0 2025-05-15 18:49:35 -03:00
package.json changelog v2.3.0 2025-05-15 18:49:35 -03:00
README.md fix: added cache to identify duplicated messages on events 2025-02-03 15:37:11 -03:00
runWithProvider.js Add Windows support for database deployment and improve error handling in runWithProvider.js 2024-11-18 20:01:10 -03:00
tsconfig.json Update ESLint configuration, Dockerfile, and package dependencies; add GitHub Actions workflow for code quality checks 2025-01-09 17:04:33 -03:00
tsup.config.ts fix: resolve build errors and audio transcription issues across chatbot services 2025-05-27 17:46:29 -03:00

Evolution Api

[Docker Image	(https://img.shields.io/badge/Docker-Image-blue)] Whatsapp Group Discord Community Postman Collection Documentation License Support Sponsors

Evolution API

Evolution API began as a WhatsApp controller API based on CodeChat, which in turn implemented the Baileys library. While originally focused on WhatsApp, Evolution API has grown into a comprehensive platform supporting multiple messaging services and integrations. We continue to acknowledge CodeChat for laying the groundwork.

Today, Evolution API is not limited to WhatsApp. It integrates with various platforms such as Typebot, Chatwoot, Dify, and OpenAI, offering a broad array of functionalities beyond messaging. Evolution API supports both the Baileys-based WhatsApp API and the official WhatsApp Business API, with upcoming support for Instagram and Messenger.

Looking for a Lightweight Version?

For those who need a more streamlined and performance-optimized version, check out Evolution API Lite. It's designed specifically for microservices, focusing solely on connectivity without integrations or audio conversion features. Ideal for environments that prioritize simplicity and efficiency.

Types of Connections

Evolution API supports multiple types of connections to WhatsApp, enabling flexible and powerful integration options:

  • WhatsApp API - Baileys:

    • A free API based on WhatsApp Web, leveraging the Baileys library.
    • This connection type allows control over WhatsApp Web functionalities through a RESTful API, suitable for multi-service chats, service bots, and other WhatsApp-integrated systems.
    • Note: This method relies on the web version of WhatsApp and may have limitations compared to official APIs.
  • WhatsApp Cloud API:

    • The official API provided by Meta (formerly Facebook).
    • This connection type offers a robust and reliable solution designed for businesses needing higher volumes of messaging and better integration support.
    • The Cloud API supports features such as end-to-end encryption, advanced analytics, and more comprehensive customer service tools.
    • To use this API, you must comply with Meta's policies and potentially pay for usage based on message volume and other factors.

Integrations

Evolution API supports various integrations to enhance its functionality. Below is a list of available integrations and their uses:

  • Typebot:

    • Build conversational bots using Typebot, integrated directly into Evolution with trigger management.
  • Chatwoot:

    • Direct integration with Chatwoot for handling customer service for your business.
  • RabbitMQ:

    • Receive events from the Evolution API via RabbitMQ.
  • Amazon SQS:

    • Receive events from the Evolution API via Amazon SQS.
  • Socket.io:

    • Receive events from the Evolution API via WebSocket.
  • Dify:

    • Integrate your Evolution API directly with Dify AI for seamless trigger management and multiple agents.
  • OpenAI:

    • Integrate your Evolution API with OpenAI for AI capabilities, including audio-to-text conversion, available across all Evolution integrations.
  • Amazon S3 / Minio:

Telemetry Notice

To continuously improve our services, we have implemented telemetry that collects data on the routes used, the most accessed routes, and the version of the API in use. We would like to assure you that no sensitive or personal data is collected during this process. The telemetry helps us identify improvements and provide a better experience for users.

Evolution Support Premium

Join our Evolution Pro community for expert support and a weekly call to answer questions. Visit the link below to learn more and subscribe:

Click here to learn more

Donate to the project.

Github Sponsors

https://github.com/sponsors/EvolutionAPI

Content Creator Partners

We are proud to collaborate with the following content creators who have contributed valuable insights and tutorials about Evolution API:

License

Evolution API is licensed under the Apache License 2.0, with the following additional conditions:

  1. LOGO and copyright information: In the process of using Evolution API's frontend components, you may not remove or modify the LOGO or copyright information in the Evolution API console or applications. This restriction is inapplicable to uses of Evolution API that do not involve its frontend components.

  2. Usage Notification Requirement: If Evolution API is used as part of any project, including closed-source systems (e.g., proprietary software), the user is required to display a clear notification within the system that Evolution API is being utilized. This notification should be visible to system administrators and accessible from the system's documentation or settings page. Failure to comply with this requirement may result in the necessity for a commercial license, as determined by the producer.

Please contact contato@evolution-api.com to inquire about licensing matters.

Apart from the specific conditions mentioned above, all other rights and restrictions follow the Apache License 2.0. Detailed information about the Apache License 2.0 can be found at http://www.apache.org/licenses/LICENSE-2.0.

© 2024 Evolution API