- Group invite info endpoint —
GET /group/invite-infoto get group details from invite link - Enhanced media sending — GIF playback, video stickers, and transparent sticker support
- Admin revoke — Allow deleting messages from others in groups (admin revoke)
- Version management — Reads version from
VERSIONfile with ldflags fallback - CORS global middleware — Applied before all routes
- Makefile compatibility — Fixed
$(shell)syntax for GNU Make 3.81 (macOS default) - CI/CD cleanup — Removed
developbranch trigger andhomologtag from Docker workflow - README updated — New links, documentation, and hosting info
- Version from VERSION file — Reads version from
VERSIONfile at startup instead of hardcoded value
- Makefile compatibility — Fixed
$(shell)syntax for GNU Make 3.81 (macOS default)
- Update whatsmeow lib
Docker: evoapicloud/evolution-go:0.5.3
- Update context handling in service methods
- Refactored multiple service methods across various packages to include
context.Background()as the first argument in client calls. This change ensures that all client interactions are properly context-aware, allowing for better cancellation and timeout management. - Updated methods in
call_service.go,community_service.go,group_service.go,message_service.go,newsletter_service.go,send_service.go,user_service.go, andwhatsmeow.goto enhance consistency and reliability in handling requests. - This adjustment improves the overall robustness of the API by ensuring that all client calls can leverage context for better control over execution flow and resource management.
- Refactored multiple service methods across various packages to include
Docker: evoapicloud/evolution-go:0.5.2
- SetProxy Endpoint: New endpoint
POST /instance/proxy/{instanceId}to configure proxy for instances- Support for proxy with/without authentication
- Validation of required fields (host, port)
- Automatic cache update via reconnection
- Integrated Swagger documentation
- CheckUser Fallback Logic: Implemented intelligent fallback logic
- If
formatJid=truereturnsIsInWhatsapp=false, automatically retries withformatJid=false - Significant improvement in valid user detection
- Added
RemoteJIDfield to use WhatsApp-validated JID
- If
- LID/WhatsApp JID Swap: Automatic handling of special cases
- When
Sendercomes as@lidandSenderAltcomes as@s.whatsapp.net - Automatic inversion:
SenderandChatreceive@s.whatsapp.net,SenderAltreceives@lid - Detailed logs for tracking swaps
- When
- SendMessage: Standardization of WhatsApp-validated
remoteJIDusage - User Validation: Improvement in phone number validation and formatting
Docker: evoapicloud/evolution-go:0.5.1
- Instance Deletion: Enhance instance deletion and media storage path resolution
- Media Storage: Improvements in media storage and path resolution
Docker: evoapicloud/evolution-go:0.5.0
- Media Storage: Enhance media storage and logging in Whatsmeow event handling
- Retry Logic: Implement retry logic for client connection and message sending
- Media Handling: Enhance media handling in event processing
Docker: evoapicloud/evolution-go:0.4.9
- Connection Handling: Add instance update test scenarios and improve connection handling
- FormatJid Field: Update FormatJid field to pointer type for better handling in message structures
- Dependencies: Update dependencies and fix presence handling in Whatsmeow integration
Docker: evoapicloud/evolution-go:0.4.8
- Audio Duration: Improve audio duration parsing in convertAudioToOpusWithDuration function
Docker: evoapicloud/evolution-go:0.4.7
- Phone Number Formatting: Improve phone number formatting and validation in user service
- Brazilian/Portuguese Numbers: Update Brazilian and Portuguese number formatting in utils
- Media Handling: Enhance media handling in event processing
Docker: evoapicloud/evolution-go:0.4.6
- User Existence Check: Add user existence check configuration and JID validation middleware
Docker: evoapicloud/evolution-go:0.4.5
- Dependencies: Update dependencies and enhance audio conversion functionality
Docker: evoapicloud/evolution-go:0.4.4
- CLAUDE.md: Add CLAUDE.md for project documentation and enhance RabbitMQ connection handling
Docker: evoapicloud/evolution-go:0.4.3
- PostgreSQL Connection: Fix in PostgreSQL connection configuration for session auth
- Controlled configuration of pool, idle, etc.
- Adjustment on top of whatsmeow lib
- User Endpoints: Fix in 'User Info' and 'Check User' endpoints
- Now return with contact's LID information
- Own Message Reactions: Additional 'fromMe' parameter using Chat id
- CreatedAt Field: CreatedAt field added to instances table
- Advanced Settings: Advanced configurations in instance creation
alwaysOnline(still to be implemented)rejectCall- Automatically reject callsmsgRejectCall- Call rejection messagereadMessages- Automatically mark messages as readignoreGroups- Ignore group messagesignoreStatus- Ignore status messages
- Advanced Settings Routes: New routes for get and update of advanced settings
- QR Code Control:
QRCODE_MAX_COUNTvariable to control how many QR codes to generate before timeout - AMQP Events:
AMQP_SPECIFIC_EVENTSvariable to individually select which events to receive in RabbitMQ
- Reconnect Endpoint: Fix in reconnect endpoint
- Sender Info:
SenderandSenderAltno longer come with session id, only the id
- QR Code Generation: Fix to not generate QR code automatically after disconnection or logout
- Base implementation of Evolution API in Go
- WhatsApp integration via whatsmeow
- Instance system
- Basic message sending endpoints
- Webhook support
- RabbitMQ and NATS integration
- Authentication system
- Swagger documentation
- The new
SetProxyendpoint requires admin permissions (AuthAdmin) - The
CheckUserfallback logic is automatic and transparent - LID/WhatsApp JID handling is automatic
- Check PostgreSQL connection settings if using postgres auth
- Review advanced settings configurations if necessary
- Configure
QRCODE_MAX_COUNTif you want to limit QR codes - Configure
AMQP_SPECIFIC_EVENTSfor specific RabbitMQ events
- Docker Hub:
evoapicloud/evolution-go - Documentation: Swagger available at
/swagger/ - GitHub: Evolution API Go
To contribute to the project:
- Fork the repository
- Create a branch for your feature
- Commit your changes
- Open a Pull Request
Last updated: October 2025