Skip to main content
WaGo serves a local API explorer from the running binary. 
http://localhost:1337/api
If your server runs on another host, replace localhost with your server address: 
https://api.your-domain.com/api

​
What it is for

Use the local API explorer when you want to:
  • Quickly inspect available endpoints on the running binary.
  • Check a request body shape while building an integration.
  • Try a request from the same environment where WaGo is deployed.
  • Compare your server response with your application code.

​
What it is not for

The API explorer is not the full product guide. It does not explain production workflows, webhook processing, media handling, call behavior, or operational troubleshooting in enough detail. Use Mintlify docs for:
  • How to connect and scan a session.
  • How to design your token flow.
  • How to receive and parse webhooks.
  • How to send media safely.
  • How to troubleshoot sessions, media, webhooks, and calls.

​
How to use it

  1. Start WaGo.
  2. Open http://localhost:1337/api.
  3. Pick an endpoint.
  4. Add the required header:
token: YOUR_TOKEN
or, for admin endpoints: 
admintoken: YOUR_ADMIN_TOKEN
  1. Send the request and compare the response with the matching Mintlify docs page.

​
Common problems

​
The page does not load

Check that WaGo is running: 
curl http://localhost:1337/server/ok
If WaGo is on a remote server, check firewall and reverse proxy rules.

​
Requests fail with Unauthorized

The request is missing the token header, or the token does not exist in WaGo.

​
Admin endpoints fail

Admin endpoints need admintoken, not token. Keep the admin token out of browser applications.

​
Browser mixed-content errors

If your web app is loaded over HTTPS, call WaGo over HTTPS too. Browsers block insecure API calls from secure pages.