---
title: "Resubscribe WhatsApp Users V2"
slug: "resubscribe-whatsapp-users-v2"
description: "Insider One's WhatsApp Resubscribe API v2 reference: POST endpoint to resubscribe up to 500 E.164 phone numbers per request, with parameters and response codes."
tags: ["resubscribe sms users", "subscribe api"]
updated: 2026-10-13T08:55:37Z
published: 2026-10-13T08:55:37Z
canonical: "academy.insiderone.com/resubscribe-whatsapp-users-v2"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://academy.insiderone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Resubscribe WhatsApp Users V2

The WhatsApp Resubscribe API enables you to update the status of an unreachable phone number to reachable in Insider One's [WhatsApp](/v1/docs/whatsapp-overview) product.

If a user exists with the provided phone number, the user's subscription status will be updated. If no user exists and the phone number is used as an identifier, a new user will be created.

> [!WARNING]
> After you collect valid consent, use the Resubscribe API to make an unsubscribed phone number reachable again. Updating only the **whatsapp_optin** attribute through the [Upsert User Data API](/v1/docs/upsert-user-data-api), a CSV upload, or the [Web SDK](/v1/docs/insider-web-sdk) does not resubscribe a number that is on the [WhatsApp global unsubscribe](/v1/docs/manage-whatsapp-global-unsubscribe) list, because the **WhatsApp Opt-Out User** attribute stays true. You can also remove the number manually under **Audience** > **Suppression** > **Global Unsubscribe**. See also: [Why is the user still unreachable after re-opting in?](https://academy.insiderone.com/docs/faq-about-whatsapp#why-is-the-user-still-unreachable-after-reopting-in).

## Endpoint and Headers

> **POST** https://contact.useinsider.com/whatsapp/v2/subscribe [](https://developers.insiderone.com/#4a7de3bd-b837-4b6f-8aa6-69b6ecd6482a)

> Visit our Postman collection to test this request.

### Headers

| Header | Sample Value | Description |
| --- | --- | --- |
| X-PARTNER-NAME | mybrand | This is your partner name. Navigate to **InOne** > **Inone Settings** > [**Account Settings**](/v1/docs/inone-account-settings) to copy your partner name. The partner name should be lowercase. |
| X-REQUEST-TOKEN | 1a2b3c4e5d6f | This key is required to authorize your request. Refer to [API Authentication Tokens](/v1/docs/api-authentication-tokens) to generate your Resubscribe token. |
| Content-Type | application/json | This header specifies the media type of the resource. |

## Body Parameters

| Parameter | Description | Data Type | Required |
| --- | --- | --- | --- |
| phone_numbers | Users' phone number in **E.164 format** (e.g., +6598765432) | String Array | Yes |

## Sample Request

The sample below displays a request to subscribe multiple users to WhatsApp communications.

Every request to the request endpoint requires a **JSON-formatted** request body containing your phone number’s content and metadata, including the subscriber’s phone number.

The **phone_numbers** field is required for resubscribe requests.

```bash
curl --location --request POST 'http://contact.useinsider.com/whatsapp/v2/subscribe' \
--header 'Content-Type: application/json' \
--header 'X-PARTNER-NAME: mybrand' \
--header 'X-REQUEST-TOKEN: a1b2c3d4e5f6' \
--data-raw '{
     "phone_numbers": [
        "+900000000000",
        "+900000000000",
        "+900000000000",
        "+900000000000",
        "+900000000000",
        "+900000000000"
    ]
}'
```

## Sample Responses

The following are some sample responses you might receive for your request.

#### 200 OK

```json
{
  "statusMessage": "OK"
}
```

#### 400 Bad Request

```json
{
  "statusMessage": "Bad request"
}
```

#### 401 Unauthorized

```json
{
  "statusMessage": "Unauthorized"
}
```

## Limitations

- All functions must be executed with a simple **HTTPS POST** request.
- Only phone numbers can be sent via this API. No data can be retrieved.
- A maximum of **500 phone numbers** can be consumed in **one request**.
- The API Key should be provided as the authorization key in the request header. If the key is incorrect, the operation will not be executed, and an authorization error will return in the response.
- The value of the X-PARTNER-NAME header should be **lowercase**.

> The default limit shown here is a standard baseline. If your use case requires higher capacity, feel free to reach out to the Insider One team. We can adjust it to fit your needs.