Dashboard
System Ready
100%
Templates
--
Total approved templates
Session
Active
Service is online and listening
Quick Help & Guidelines
- Text messages work only inside the 24-hour window after user reply.
- If no open window, send an approved template first.
-
Use recipient in E.164 digits only, e.g.
919482878752. - URL button template parameters must be ≤ 15 characters.
Core Configuration
Essential credentials for WhatsApp Cloud API
Settings are saved locally on the server.
Saved Profiles
Store and switch between multiple WhatsApp account configurations
No profiles saved yet.
Debug Output
Setup Wizard
Follow these steps sequentially to configure your WhatsApp Business account.
Check App Subscription
Verify if your Meta App is correctly linked to the WhatsApp Business Account.
Subscribe App to WABA
Manually trigger the subscription if step 1 returned an empty array.
Check Phone Number Status
Ensure the phone number is verified and ready for messaging.
Phone Verification (OTP)
Only required if the number is not yet registered.
Token Permission Check
Deep dive into token scopes and app bindings.
Create Template
Submit a new message template for Meta approval.
Meta Approval Tips
- Keep variable density low (0-2 placeholders per template).
- Use clear, transactional wording.
- Include your brand name in the body.
Final Validation
Fetch your approved templates and send a test message.
Send Template
Initiate conversations using approved templates
Send Text
Free-form messaging within the 24h window
Graph API Endpoints
Documentation of the underlying requests made by this tool.
Curl Requests (Reference)
Includes onboarding, register, template create/send, token checks, and whoami.
Checks app subscription to WABA. Used to confirm app linkage before send operations.
Used by: Step 1, Token Permission Check Extensions: app-id mismatch warning, subscription drift history.
Subscribes app to WABA. Usually idempotent and safe to retry.
Used by: Step 2 Extensions: add unsubscribe action, automatic post-check status badge.
Reads phone readiness fields (display number, verified name, code status, quality).
Used by: Step 3, Token Permission Check Extensions: include name_status/platform_type, periodic poll mode.
Requests verification code by SMS/VOICE for number onboarding.
Used by: Step 4 Extensions: cooldown timer UI, locale presets.
Verifies OTP code and completes number verification.
Used by: Step 5 Extensions: mask OTP in logs, auto-run phone status after success.
Registers phone for Cloud API messaging. Required to clear #133010.
Used by: Curl reference/manual flow Extensions: dedicated UI step with PIN input and post-register checks.
Creates templates for approval workflow.
Used by: Step 7 Extensions: variable-density linter, category-aware schema helper.
Fetches templates with status/category/language/components.
Used by: Step 8, Messaging template picker Extensions: status filters, pending-to-final polling.
Sends template messages, including components/parameters.
Used by: Step 9 + Messaging tab Extensions: render preview, stronger component validation.
Sends free-form text inside the 24h customer-care window.
Used by: Step 10 + Messaging tab Extensions: auto-fallback guidance to templates when window is closed.
Token introspection: validity, app binding, scope list, type, subject id.
Used by: Step 6 Token Check + Who Am I Extensions: auto-highlight missing scopes.
Identifies the token subject currently used by runtime config.
Used by: Step 6 Who Am I Extensions: map subject ID to expected system-user ID locally.
Need deeper integration?
Check the official Meta Graph API documentation for webhooks and business management.
Official Docs