Skip to main content
Postman is a tool for testing and exploring REST APIs visually and intuitively. With the official Evolution Go collection, you can execute requests, configure environments, and explore all endpoints without writing any code.

Prerequisites

  • Evolution Go installed and running — see the installation guide
  • Postman installed — download here
  • Your API Key (GLOBAL_API_KEY configured in your .env)

Step 1: Import the Official Collection

The official Evolution Go collection is publicly available on Postman and includes all API endpoints ready to use.
1

Open Postman

Open Postman on your computer or access Postman Web.
2

Access Import

In the upper left corner, click Import.
3

Import via link

Select the Link tab and paste the official collection URL:
4

Confirm import

Click Continue and then Import. The Evolution Go collection will appear in your sidebar.

Step 2: Create the Environment

Environment variables centralize your instance configurations, allowing you to switch between environments (local, staging, production) without modifying each request.
1

Create new Environment

In Postman, click Environments (eye icon in the upper right corner) and then + to create a new one.
2

Name the Environment

Name it Evolution Go (or any name you prefer).
3

Add variables

Add the following variables:
4

Save and activate

Click Save and select the Evolution Go environment in the selector in the upper right corner of Postman.
Never share or expose the api_key value publicly. It provides full access to your API.

Step 3: Configure Collection Headers

To avoid adding headers to each request individually, configure them at the collection level.
1

Open collection settings

Right-click on Evolution Go in the sidebar and select Edit.
2

Access the Variables tab

Confirm that the variables base_url, api_key, and instance_id are referenced.
3

Configure Pre-request Script (optional)

Optionally, add default headers to all requests via Pre-request Script:
Required authentication headers are:
  • apikey: your GLOBAL_API_KEY
  • instanceId: instance UUID (required on routes that operate on a specific instance)
  • Content-Type: application/json (for requests with a body)

Step 4: Test the Connection

Before creating instances, verify that Evolution Go is accessible. Request:
A successful response indicates the server is running. If you get a connection error, verify that Evolution Go is running and that base_url is correct.

Step 5: Create a WhatsApp Instance

With the connection verified, create your first instance. Request:
Headers: Body:
Success response:
Copy the instanceId from the response and save it to the instance_id variable in your Environment to use in subsequent requests.

Step 6: Connect to WhatsApp

With the instance created, start the WhatsApp connection. This endpoint also allows you to configure the webhook to receive events. Request:
Headers: Body:
After the request, you’ll receive a QR Code via webhook (field qrcode in base64). Scan it with your WhatsApp mobile app at Settings > Linked Devices > Link a Device.
To connect via Pairing Code instead of QR Code, add the phone field to the body with the phone number in the format 5511999999999.

Exploring More Endpoints

Access the Swagger interactive documentation of your instance to discover all available endpoints:
Swagger lets you visualize parameters, test endpoints directly in the browser, and see response examples.

Next steps

Configure Webhooks

Receive real-time events for messages, connections, and more

Initial Setup

Manage instances through the Evolution Go visual panel