Developers
Loading developer console…
Fetching API keys, webhooks, deliveries, and request logs.
Loading developer console…
Fetching API keys, webhooks, deliveries, and request logs.
Manage API keys, webhooks, and inspect Public API traffic for your organization.
Stable, key-authenticated endpoints for server-side integrations.
https://dashboard.wacommerce.id/api/public/v1# GET /me — verify your key and tenant
curl -H "Authorization: Bearer nxk_live_xxx" \
https://dashboard.wacommerce.id/api/public/v1/me
# GET /chats — list WhatsApp chats
curl -H "Authorization: Bearer nxk_live_xxx" \
https://dashboard.wacommerce.id/api/public/v1/chats
# POST /messages — send a WhatsApp message
curl -X POST https://dashboard.wacommerce.id/api/public/v1/messages \
-H "Authorization: Bearer nxk_live_xxx" \
-H "Content-Type: application/json" \
-d '{"to":"+628123456789","body":"Hello from the Public API"}'/meKey + tenant identity/chatsList WhatsApp chats/chats/:phoneSingle chat thread/ordersList orders/messagesSend a WhatsApp messagenxk_live_AbC123… shown in the API Keys table) instead of the full token. The prefix is only an identifier — authenticate with the complete nxk_live_ token shown once at creation. A 401 can also mean the key was revoked or never existed./api/auth/login is dashboard session auth, not for API keys. Use a nxk_live_ bearer token instead./api/proxy/* is the internal dashboard proxy, not for external developers. Call /api/public/v1/* directly.