WhatsApp Authentication (OTP)
Send and verify one-time passcodes on your WhatsApp Business number via ProfilePilot’s API for ecommerce login, account recovery, and staff portals.
WhatsApp Authentication is separate from Orders and Marketing. It uses Meta Authentication templates on your organisation’s connected WABA. Admins enable WA Auth on the organisation; staff then configure defaults under Dashboard → WhatsApp Auth.
In WhatsApp Manager, create templates with category Authentication and Copy code. Sync them on the Auth page, choose a default (for example verify_user, language en), set country code and TTL to match the template (often 600 seconds), then Save.
Create an API key on the Auth page and store the full ppwa_ key securely — it is shown once. Your app calls POST /api/v1/whatsapp/auth/otp/send and /otp/verify with Authorization: Bearer and x-org-id set to your organisation UUID. Dashboard Test send/verify is only for allow-listed operational numbers.
Moving from WATI or another ESP: attach your existing WABA in Connect WhatsApp, approve Auth templates, create the ProfilePilot API key, then hard-cut OTP traffic to ProfilePilot. Avoid two systems sending OTPs on the same WABA at once.
Meta bills Authentication (and Authentication international) on the WABA card. ProfilePilot usage appears on the Auth page KPIs and under Orders → Usage when metering is live.
- Confirm WA Auth is enabled for your organisation
- Connect WhatsApp (client-owned WABA) if not already connected
- Approve Authentication templates in WhatsApp Manager and Sync
- Set default template, language, country code, TTL — Save
- Create an API key and store it in your app secrets
- Test send + verify on an allow-listed number, then integrate send/verify APIs
AI answers may be approximate. Verify critical steps in official docs above.