Define an API base path?

[goleadev]

Hello,

Is it possible to define a base path for the API? Currently, all API calls need to be made to http://localhost:3000 (e.g. http://localhost:3000/api/session/start). Is it possible to change this to something like http://localhost:3000/waha (e.g. http://localhost:3000/waha/api/session/start)?

[allburov]

Hi! It doesn't support it. You can run nginx close to the WAHA and proxy requests there

[allburov]

It may help:

docker-compose.yaml

version: '3'
services:
  nginx:
    image: nginx
    ports:
      - "3000:80"
    volumes:
      - ./nginx.conf:/etc/nginx/nginx.conf
    depends_on:
      - app
  app:
    image: whatsapp-http-api

nginx.conf

worker_processes 1;

events { worker_connections 1024; }

http {
  server {
    listen 80;
    server_name localhost;

    location /waha/ {
      proxy_pass http://app:3000/api/;
      proxy_set_header Host $host;
      proxy_set_header X-Real-IP $remote_addr;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }
  }
}

docker-compose up

[goleadev]

The api indeed, is working. Unfortunatelly the swagger page is still making calls to /api instead of /waha/api so the server returns 404.

[allburov]

Goot it, will look at this!

[allburov]

Hi! @goleadev

1. Published new PLUS version today with the fix - now you can change server parameters in Swagger
   

2. Added a task for configuring base path via environment variables, so no proxy is required (don't know when it'll be done tho) - Define an API base for API - Endpoints and FILES #96

[allburov]

FYI - we had to hide the advanced configuration by default in WAHA 2023.6. You can enable it by setting WHATSAPP_SWAGGER_CONFIG_ADVANCED=True environment variable