Creates a WhatsApp OTP message request. Only to is required. If both otpMode and code are omitted, Wevlix generates the six-digit code. Supplying code without otpMode is valid and infers provided mode. In live mode, Wevlix selects an approved, sendable AUTHENTICATION template from the project WhatsApp account: it prefers the exact requested locale, then an eligible variant of the same language. If no matching language is available, the request is rejected before billing or queueing. Shared accounts also require project template access. Newly connected verified businesses with no existing templates normally receive the wevlix_otp_en and wevlix_otp_ar starters, but this endpoint does not guarantee either template name. Generated and provided modes use the same selected template. In sandbox mode or with a development key, delivery is simulated without an upstream call or billing. Use clientMessageId for retry-safe idempotency.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
400The payload is invalid. Common conflicts are otpMode=provided without code, otpMode=generated with code, or a code that is not exactly four or six digits.
401Missing or invalid API key.
403OTP sending is not allowed for this API key, the development-key phone allow-list, project WABA state, or project balance.
