> For the complete documentation index, see [llms.txt](https://docs.360dialog.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.360dialog.com/docs/messaging/message-types/address.md).

# Address

This page describes how to send address messages on the WhatsApp Business Platform.

{% hint style="info" %}
This feature is only available for businesses based in India and their India customers.
{% endhint %}

### Address Message Request

<mark style="color:orange;">`POST`</mark> `https://waba-v2.360dialog.io/messages`

Address messages provide a structured way for WhatsApp users to share a delivery or shipping address with a business directly within a conversation.

Address messages are interactive messages composed of four main components: **header**, **body**, **footer**, and **action**. Within the action component, the business defines the action name `address_message` together with the required parameters.

**Headers**

| Name          | Value              |
| ------------- | ------------------ |
| Content-Type  | `application/json` |
| Authorization | `D360-API-KEY`     |

**Body Example**

```json
{
  "messaging_product": "whatsapp",
  "recipient_type": "individual",
  "to": "<PHONE_NUMBER>",
  "type": "interactive",
  "interactive": {
    "type": "address_message",
    "body": {
      "text": "Thanks for your order! Tell us what address you’d like this order delivered to."
    },
    "action": {
      "name": "address_message",
      "parameters": {
        "country": "<COUNTRY_ISO_CODE>"
      }
    }
  }
}
```

**Response**

{% tabs %}
{% tab title="200" %}

```json
{
  "contacts": [
    {
      "input": "text",
      "wa_id": "text"
    }
  ],
  "messages": [
    {
      "id": "text",
      "message_status": "accepted"
    }
  ],
  "messaging_product": "text"
}
```

{% endtab %}

{% tab title="400" %}

```json
{
  "error": "Invalid request"
}
```

{% endtab %}
{% endtabs %}

### Error Handling

If the phone number’s country code does not match the selected country, the address message cannot be requested. For example, an address message cannot be sent to a recipient whose country is set to India but whose phone number uses the country code `+65`.

After the address message is sent, the business must wait for the recipient to complete and submit the address form. The submitted address details are delivered through the configured [webhook](https://docs.360dialog.com/docs/hub/webhook-url.md) endpoint.<br>

### Address Message Steps

1. The business sends an address message to the recipient using the action name `address_message`.
2. The recipient interacts with the message by selecting the call-to-action (CTA), which opens the address message screen. The recipient completes the address form and submits it.
3. After the form is submitted, a webhook notification is sent to the configured endpoint containing the address details provided by the recipient.

The address message flow consists of the following steps:

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.360dialog.com/docs/messaging/message-types/address.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
