Root API migration

QaziHost WhatsApp API accepts the QaziHost root API paths, access_token and instance_id. Create an access token in Dashboard → API keys, copy your instance ID, and replace the API hostname in your integration with this site's address (the examples below already use it).

Routes marked "live verified" were exercised end to end against a linked WhatsApp number on 2026-09-13. Routes marked "mocked" pass automated tests that run the real request handling, validation, tenant isolation and SQLite persistence against a recorded mock of the WhatsApp transport; routes marked "untested" are implemented but have no automated test. Webhook payload parity is pending; existing incoming events use the QaziHost format described in the main documentation.

curl -X POST "https://your-platform-domain.com/send" \
  -H "Content-Type: application/json" \
  -d '{"number":"923001234567","type":"text","message":"Hello","instance_id":"YOUR_INSTANCE_ID","access_token":"YOUR_ACCESS_TOKEN"}'

JSON and URL-encoded forms are accepted. GET parameters go in the query string. Existing account-scoped API keys also work as access_token for their own instance. User-wide access tokens can create and manage all of your instances. Local SQLite storage is initialized automatically.

Current limits: media downloads are capped at 16 MiB; local/private network media URLs are rejected. Live location, business-profile editing, catalog sends, community events, call links and channel admin invitation/acceptance are not implemented. Channel lists and LID mappings depend on data received or fetched by this instance. Media retrieval by WhatsApp message ID and some optional parameters still need implementation. Labels are stored locally; label synchronization is pending.