WizMessage provides a developer-friendly API that lets you connect your existing systems — your e-commerce store, CRM, helpdesk, or custom application — to drive chatbot actions, manage contacts, and send bulk messages programmatically. From this screen, you generate and manage API keys with enterprise-grade security: keys are hashed for safe storage, secrets are shown only once, and you can restrict access by IP whitelist and enforce rate and daily request limits. Set up outbound webhooks to receive real-time events (message received, delivered, read) with signature verification, and use the built-in Playground to test live API calls directly from your browser before writing any integration code.
API & WEBHOOK ARCHITECTUREADMIN1Generate KeysAdmin creates API key and secret.DEVELOPER2Integrate APIDeveloper uses keys in external software.SYSTEM3Event OccursMessage sent or delivered triggers a webhook.SYSTEM4Webhook DeliveryPayload signed and sent to developer server (up to 5retries).DONE
📊 Plan Requirement: API Management requires Wiz Bot or Wiz Pro. API calls and webhook deliveries are unlimited — no monthly message cap applies to API usage.
Generate API Keys — create secure API keys (pk_live_...) and single-view secrets (sk_live_...) to connect external systems.
Rotate Secrets — if compromised, regenerate your secret while keeping the public key intact to avoid full code refactoring.
Enforce IP Whitelisting — define a comma-separated list of allowed IP addresses to block unauthorized requests.
Set Usage Limits — mitigate abuse by defining rate limits (requests per minute) and daily absolute caps.
Configure Webhooks — set up outbound webhooks with a signature token (whsec_...) to receive real-time events (sent, delivered, received).
Test in the Playground — use the built-in, in-browser Playground to execute live test calls using your templates and contacts before writing code.
WHAT YOU CAN DOWizMessageOne dashboard, every channelGenerate API KeysCreate secure public and secret keypairsRotate SecretsRegenerate secrets without breakingkey IDsIP WhitelistingRestrict access to allowed IPaddressesUsage LimitsEnforce rate and daily requestlimitsWebhooksReal-time events with signatureverificationAPI PlaygroundTest live calls directly in yourbrowserWHAT YOU CAN DOWizMessageOne dashboard, every channelGenerate API KeysCreate secure public and secret key pairsRotate SecretsRegenerate secrets without breaking key IDsIP WhitelistingRestrict access to allowed IP addressesUsage LimitsEnforce rate and daily request limitsWebhooksReal-time events with signature verificationAPI PlaygroundTest live calls directly in your browser
YOUR API INTEGRATION WORKFLOWSTARTDONESTEP 11Generate KeysCreate a new API key, set rate limits and IPwhitelists, and copy the Secret Key (it is onl…STEP 22Test in PlaygroundOpen the Playground tab, select your key,configure message parameters, and send a live…STEP 33Configure WebhooksSet up a webhook URL to receive events, and usethe generated Webhook Secret to verify payload…YOUR API INTEGRATION WORKFLOWSTEP 11Generate KeysCreate a new API key, set rate limits and IPwhitelists, and copy the Secret Key (it is only shown…STEP 22Test in PlaygroundOpen the Playground tab, select your key, configuremessage parameters, and send a live test request.STEP 33Configure WebhooksSet up a webhook URL to receive events, and use thegenerated Webhook Secret to verify payload signatures.DONE
Tip: Treat API keys like passwords. Never commit them to Git repositories or hardcode them in frontend code. If a key is leaked, revoke or rotate it immediately.
API Key Format: Prefixed with pk_live_ (e.g., pk_live_abcd1234...). The first 12 characters are plain text for identification; the full key is hashed via SHA-256.
API Secret Format: Prefixed with sk_live_ (e.g., sk_live_xyz9876...). Shown only once upon creation.
Rate Limit: Maximum allowed requests per minute per key (defaults to 60).
Daily Limit: Hard daily cap on total requests per key (defaults to 1000).
The API turns WizMessage from a standalone tool into a connected part of your business operations.
WHATSAPP VS EMAILWhatsAppEmailOf abandoned carts recoveredusing automated WhatsApp…15-25%Email — far lowerReturn on investment for anonline brand using cart…140×Reduction in "Where is myorder?" tickets using order…40-70%Email — far lowerWHATSAPP VS EMAILWhatsAppEmailOf abandoned carts recovered usingautomated WhatsApp reminders15-25%Return on investment for an onlinebrand using cart recovery140×Reduction in "Where is my order?"tickets using order webhooks40-70%
PLAYBOOK: HIGH-RETURN INTEGRATIONSDAY 1RESULTSSALESCart RecoveryConnect your e-commerce store to send aWhatsApp reminder 30–45 minutes after cartabandonment. Yields far better recovery than…1SUPPORTOrder UpdatesSend automated status updates (packed,shipped, delivered) to drastically reduceroutine support tickets.2OPERATIONSCRM SyncSync every interaction back to HubSpot, Zoho,or Salesforce so sales and support teamsshare a unified customer view.3PLAYBOOK: HIGH-RETURN INTEGRATIONS1SALESCart RecoveryConnect your e-commerce store to send a WhatsAppreminder 30–45 minutes after cart abandonment.Yields far better recovery than email.2SUPPORTOrder UpdatesSend automated status updates (packed, shipped,delivered) to drastically reduce routine supporttickets.3OPERATIONSCRM SyncSync every interaction back to HubSpot, Zoho, orSalesforce so sales and support teams share aunified customer view.