Twilio is launching a new Console. Some screenshots on this page may show the Legacy Console and therefore may no longer be accurate. We are working to update all screenshots to reflect the new Console experience. Learn more about the new Console.
WhatsApp is the most popular messaging app in many parts of the world. With the WhatsApp Business Platform with Twilio, you can send notifications, have two-way conversations, and build chatbots. If you're trying to reach and better converse with users in LATAM, EMEA, and APAC, then you need to consider using WhatsApp.
WhatsApp has 3 messaging products:
- WhatsApp Consumer app, with users around the globe;
- WhatsApp Business app, generally used by small businesses and micro businesses; and
- WhatsApp Business Platform, previously known as the WhatsApp Business API
Twilio offers access to the WhatsApp Business Platform. Developers can use WhatsApp with all of Twilio's products, including the Programmable Messaging API, Conversations API, Twilio Flex and Studio. For more information, please see WhatsApp Business Accounts with Twilio.
WhatsApp requires that your application implement explicit user opt-ins to deliver messages over WhatsApp. You may gather this opt-in information either via a web page or a mobile app, such as during your application's sign-up flow, in your application's account settings, via SMS, etc. WhatsApp also requires businesses to respect opt-out requests from end users to maintain high number quality.
Please note that sending messages to end users without an opt-in may result in users blocking your business and may ultimately lead to the suspension of your WhatsApp Business account.
On WhatsApp, users message each other using their phone numbers as identifiers. To send and receive WhatsApp messages using the Twilio Programmable Messaging API, you'll need a phone number as well. The Twilio API addresses WhatsApp users and your numbers, using the following prefixed address format:
whatsapp:<E.164 formatted phone number>
(E.164 is an international telephone number format; you will see it often in the strings that represent Twilio phone numbers.)
To use WhatsApp messaging in production apps, you must enable WhatsApp on your Twilio number. For a step-by-step walkthrough of the process, visit our Self-Signup Guide for WhatsApp. If you are registering for WhatsApp on behalf of a third party, such as one of your clients, then you may be an Independent Software Vendor (ISV) – please follow our Guided Signup process instead.
For information about using a non-Twilio number with WhatsApp, check out our Support guide Can I activate my own phone number for WhatsApp on Twilio?
WhatsApp uses your Meta Business Manager account to identify your business and associate your WhatsApp Business Account (WABA) with it. To scale with WhatsApp, you will also need to verify your Meta Business Manager account. You can create or connect your Meta Business Manager account through Twilio's Self-Signup process in the Console.
If you are an ISV, you will need to provide Twilio with your Meta Business Manager ID before you or your end clients begin onboarding. If you do not already have a Meta Business Manager account, follow Facebook's instructions to create one. Your Meta Business Manager ID can be found in the "Business Info" section under Business Settings.
You can register new numbers for WhatsApp directly in the Twilio Console by following our Self-Signup Guide for WhatsApp. If you are an ISV following our Guided Signup process, you will need to request to have WhatsApp numbers registered by Twilio's Operations team. As part of the onboarding process, either you or Twilio's Operations team will create a WhatsApp Business Account (WABA) and associate it with your Twilio Account Sid. Only one WABA is allowed per Twilio Account at this time.
Please note that as of January 2023, WhatsApp has imposed new limitations on phone numbers and WABAs:
- Phone Number limits applied across all WABAs per single Meta Business Manager
- Businesses that don't have a verified Meta Business Manager are allowed a max of 2 phone numbers per Meta Business Manager across all WABAs.
- Businesses with a verified Meta Business Manager account can have up to 20 phone numbers. An exception for up to 50 phone numbers can be requested by opening a support ticket. Higher limits may be made available with a second appeal and a valid use case justification, at WhatsApp's discretion.
- WABA limits:
- Businesses with a verified Meta Business Manager can have a max of 20 WABAs across their Meta Business Manager.
- Businesses that have an Official Business Account (OBA) are allowed up to 1000 WABAs.
Please note that most businesses that onboarded prior to January 2023, and those with higher limits previously, are exempt from these limitations. WhatsApp reserves the right to restrict the numbers and WABAs for any reasons and if they see any evidence of scams or severe spam on an account, at their discretion.
Once your number has been enabled for WhatsApp, it can be used as a WhatsApp Sender. Clicking on a specific Sender takes you to its specific Configuration page. This includes the Endpoint configuration section, where you can specify what action Twilio should take when it receives a WhatsApp message at this number. You can configure this sender as part of a Messaging Service or with an individual webhook URL.
You can also update all your profile details here.
WhatsApp requires that business-initiated notifications sent by your application be templated and pre-registered, with the exception of messages sent as a reply to a user-initiated message. (See Conversational Messaging on WhatsApp for more details). To manage your own templates and your WhatsApp profile, go to Messaging > Senders > WhatsApp Senders in the Console. Here, you can see the list of your WhatsApp-enabled Twilio phone numbers (senders) as well as any templates that you have submitted for approval.
To learn more, consult our Guide to Sending WhatsApp Notifications Using Message Templates.
To have 2-way conversations with end users, you need to be able to receive messages from them. Users can send your business messages either directly or in response to a templated notification.
A WhatsApp session begins when a user sends a message to your app. Sessions are valid for 24 hours after the most recently received message, during which you can communicate with customers using free-form messages. To send a message outside the 24-hour session window, you must use a pre-approved message template. (See our Guide to WhatsApp Message Templates).
When customers send you a WhatsApp message, Twilio sends a webhook (a request to a URL that you specify) to your application. You can configure the URL to which Twilio sends a webhook when it receives inbound messages in the Twilio Console:
- on the Sandbox page
- on the page for WhatsApp-enabled numbers
- under the "Integration" section of your settings for a specific Messaging Service (Under the Messaging Services section of the Console)
Optionally, you can configure a Fallback URL in the same place that you set your default webhook URL. If a fatal error occurs while making a request to your primary webhook URL, Twilio "falls back" to this secondary fallback URL.
When making the request to your fallback URL, Twilio also submits the
ErrorUrl parameters, indicating the error code of the failure and the URL for which the failure occurred.
|Configuring Inbound Message Webhooks for Twilio Sandbox for WhatsApp
|Configuring Inbound Message webhooks for your WhatsApp enabled Twilio number
For details on the data provided in the request that Twilio makes to your application (via the webhook URL), read more about Twilio's HTTP Requests to Your a Application.
The webhook for inbound messages uses the same format as incoming SMS and MMS messages, with the exception that
From addresses will be set to WhatsApp addresses (
whatsapp:<your E.164 number> and
whatsapp:<User's E.164 phone number>), respectively.
Incoming messages may include text or media. The
Body field contains the message text, and the
MediaUrl0 field contains a link to the media file. You can learn how to download incoming media included in a message in the Receive and Download Images on Incoming MMS Messages tutorial. Supported media include images (JPG, JPEG, PNG), audio files, and PDF files, with a size limit of 16MB per message.
WhatsApp incoming messages are fully supported by TwiML, allowing you to seamlessly use your existing SMS app with WhatsApp. For more information, check out Documentation on How to Use TwiML.
Within a WhatsApp session, you can send freeform messages using the Programmable Messaging API. Freeform messages may include text, media and certain rich messages created with Content Templates.
Freeform WhatsApp messages that include web links will display a web page snippet preview when received on the WhatsApp client.
To receive real-time status updates for outbound messages, you can choose to set a Status Callback URL. Twilio sends a request to this URL each time your message status changes to one of the transition values in the Message Status Callback Event Flow diagram.
You can set the Status Callback URL in the Console, or when you send an individual outbound message, by including the StatusCallback parameter. You can set the status callback URL in different parts of the Twilio Console depending on your messaging setup:
- For the WhatsApp Sandbox or an individual WhatsApp Sender –read WhatsApp and other messaging channels for additional properties that Twilio sends to your callback URL
- For a Messaging Service (under the Integration settings for a specific Messaging Service) – read the status callback with a Messaging service guide for configuration options
When you set the Status Callback URL, Twilio sends a POST request to that URL, including the message
sid (the Message's Unique identifier) and other standard request parameters as well as a
status and an associated
error_code if any. Refer to the API Reference for the Message Resource for a list of parameters that Twilio sends to your callback URL.