Contacts and Location Messages
See how to use the message node to send contacts or location messages and how to report and block contacts.
Last updated
See how to use the message node to send contacts or location messages and how to report and block contacts.
Last updated
You can only send a location message up until 24 hours after receiving a message from the user. If you have not received a message from the user within this time, you will need to start a new conversation by sending a Template message.
To send location messages, make a POST call to the /messages endpoint and attach a message object with type=location. Then, add a location object.
POST https://waba-v2.360dialog.io/messages
| Name | Type | Description |
|---|---|---|
The location message will look like this to the end user:
As announced in November 2023, Meta is transitioning to a fully Cloud-hosted WhatsApp Business Platform and will stop supporting On-Premise API in October 2025. Starting from On-Premise client v2.53, all new feature updates will be exclusively delivered to Cloud API. While the On-Premise API client will receive quarterly releases, they will focus solely on bug fixes and security patches.
POST https://waba.360dialog.io/v1/messages
To send contact messages, make a POST call to the /messages endpoint and attach a message object with type=contacts. Then, add a contacts object.
POST https://waba-v2.360dialog.io/messages
Inside contacts, you can nest the following objects: addresses, emails, name, org, phone, and urls. Pluralized objects are to be wrapped in an array as shown in the example below.
Example of a contacts object with pluralized objects nested inside:
The contact message will look like this to the end user:
As announced in November 2023, Meta is transitioning to a fully Cloud-hosted WhatsApp Business Platform and will stop supporting On-Premise API in October 2025. Starting from On-Premise client v2.53, all new feature updates will be exclusively delivered to Cloud API. While the On-Premise API client will receive quarterly releases, they will focus solely on bug fixes and security patches.
POST https://waba.360dialog.io/v1/messages
Currently, it is not possible to block or unblock contacts in the Cloud API. Please refer to Meta Support regarding this limitation.
If you block a number in On-premise and then migrate to Cloud API, the number will remain blocked without the option to unblock it.
As announced in November 2023, Meta is transitioning to a fully Cloud-hosted WhatsApp Business Platform and will stop supporting On-Premise API in October 2025. Starting from On-Premise client v2.53, all new feature updates will be exclusively delivered to Cloud API. While the On-Premise API client will receive quarterly releases, they will focus solely on bug fixes and security patches.
To block a contact, you must have received a message from them within the last 24 hours.
Submit an API call to /v1/contacts/{phone_number}/block with a reason for blocking another business account.
When successful, the response will have HTTP status 200and will come without the "errors" object. The failed response looks like this:
blocking parametersThe following parameters are supported by POST calls to /v1/contacts/{phone_number}/block:
To unblock a contact, send an API call to/v1/contacts/{phone_number}/unblock
When successful, the response will have HTTP status 200and will come without the "errors" object.
The failed response looks like this:
unblock parametersThe following parameters are supported by POST calls to /v1/contacts/{phone_number}/unblock:
Here's how to get a list of your blocked contacts.
Send an API call to /v1/contacts/blocklist to receive a paginated list of your blocked contacts.
You will receive a response with a page from your block list and paging information.
block list parametersThe following parameters are supported for GET calls to /v1/contacts/blocklist:
To report a contact, you must have received a message from them within the last 24 hours.
Send an API call to /v1/contacts/{phone_number}/report including a reason if you are blocking another business account.
When successful, the response will have HTTP status 200and will come without the "errors" object.
The failed response looks like this:
reporting parametersThe following parameters are supported by POST calls to /v1/contacts/{phone_number}/report:
| Name | Description |
|---|---|
| Name | Type | Description |
|---|---|---|
| Name | Type | Description |
|---|---|---|
| Name | Description |
|---|---|
| Name | Type | Description |
|---|---|---|
| Settings | Description |
|---|---|
| Settings | Description |
|---|---|
| Settings | Description |
|---|---|
| Settings | Description |
|---|---|