Address Messages
Updated: Nov 7, 2025 This feature is only available for businesses based in India and their India customers. Address messages give your users a simpler way to share the shipping address with the business on WhatsApp. Address messages are interactive messages that contain the 4 main parts:header, body, footer, and action. Inside the action component business specifies the name “address_message” and relevant parameters.
Below table outlines the fields that are supported by the address message.
| Field Name | Display Label | Input Type | Supported Countries | Limitations |
|---|---|---|---|---|
name | Name | text | India | None |
phone_number | Phone Number | tel | India | Valid phone numbers only |
in_pin_code | Pin Code | text | India | Max length: 6 |
house_number | Flat/House Number | text | India | None |
floor_number | Floor Number | text | India | None |
tower_number | Tower Number | text | India | None |
building_name | Building/Apartment Name | text | India | None |
address | Address | text | India | None |
landmark_area | Landmark/Area | text | India | None |
city | City | text | India | None |
state | State | text | India | None |
Sample API call
This is a sample API call for the address message. Thecountry attribute is a mandatory field in the action parameters. If it is not included, there will be a validation error.
Error Handling
If the area code of the phone number for the given country is not correct, businesses will be unable to request the address message from the recipient. For example, businesses will be unable to request an address message from a recipient that has the country as “India” but has a phone number with an area code of “65”. Once the address message is sent, the business waits for the user to fill in the address and send it back. The user entered address is shared through the webhook registered in the setup process.Address Message Steps
The steps involved in an Address Message are the following: Business sends an address message with the action nameaddress_message to the user
User interacts with the message by clicking on the CTA, which brings up an Address Message screen. The user fills out their address and submits the form
After the address message form is submitted by the user, the partner receives a webhook notification, which contains the details of the address submitted by the user
Sample India Address Message



The following sequence diagram shows a typical integration flow for an address message.
Additional Action Parameters
The business can pass additional attributes such asvalues, validation_errors, or saved_addresses as part of the interactive action parameters. You can find information on each of their usage below.
| Action Parameter | Usage |
|---|---|
values | Businesses prefill this for address fields (eg. prefilling the city address field with “India”) |
saved_addresses | For businesses, they can pass in saved addresses previously associated with the user. For users, they are presented with the option to choose the saved address instead of manually filling it in |
validation_errors | Businesses can throw errors in the address fields and WhatsApp will prevent the user from submitting the address until the issue(s) are/is resolved. |
Send Address Message to a User
Make aPOST call to /<PHONE_NUMBER_ID/messages using the WhatsApp API to send an end-to-end encrypted address message to the user:
Check Your Response
A successful response includes amessages object with an ID for the newly created message.
Send an Address Message with Validation Errors
An address message should be re-sent to the user in the case of a validation error on the business server. The business should send back the set of values previously entered by the user, along with the respective validation errors for each invalid field, as shown in the sample payloads below.Receive Notifications for Address Submissions
Businesses will receive address submission notifications through webhooks, such as the one shown below.| Field Name | Type | Description |
|---|---|---|
interactive | Object | Holds the response from the client |
type | String | Would be nfm_reply indicating it is a Native Flow Response (NFM) from the client |
nfm_reply | Object | Holds the data received from the client |
response_json | String | The values of the address fields filled by the user in JSON format that are always present |
body (Optional) | String | Body text from client, what the user sees |
name (Optional) | String | Would be address_message indicating the type of NFM action response from the client |
Feature Not Supported
In the case where the client does not supportaddress_message, messages are silently dropped and an error message is sent back to the business in a webhook. The webhook notification that would be sent back is shown below:

