> For the complete documentation index, see [llms.txt](https://help.pickyassist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pickyassist.com/api-documentation-v2/whatsapp-settings-apis/whatsapp-status-update.md).

# WhatsApp Status Update

{% hint style="danger" %}

## **This feature is currently not supported  for WhatsApp Web Automation due to the recent changed by WhatsApp Web Versions** 

{% endhint %}

## Introduction 

This API allows you to post WhatsApp Status Message programmatically using the API which helps you to post Image, Video, Text as your WhatsApp Status.

![](/files/-MWV4OEPph2UXVarFXEQ)

## Important Notes

The status will broadcast only if your Privacy status is enabled, who can see your Status, make sure it's always set to "My Contacts" under the **WhatsApp -> Account -> Privacy -> Status**

{% hint style="info" %}
The Status will work only if the contact is stored in both phones i.e your contact should be saved in your customer contact and your customer contact should be saved in your phone.\
\
There is no option to delete the Status through API, however you can edit / delete manually from the phone anytime.\
\
Supports Only Image/Video/Text for the status update and text character will be around 1000 (may vary), you can add emoji in the status text 

When you add text & image/video the text may not be clickable however if you post the status only with text then the links are clickable.

When you post text message status there is no option to change the background color so the default theme color will be the background color.

If you have a huge contact list then status sending may take la onger time and may lead to the slowness of the phone which may affects the automation.
{% endhint %}

## API Variables 

| API Variable | Description                       | Mandatory                                     |
| ------------ | --------------------------------- | --------------------------------------------- |
| token        | Your API Token                    | Required                                      |
| application  | 10                                | Required                                      |
| media        | Public URL of your Video / Image  | Optional if the text is not blank             |
| media\_code  | Base 64 code of the Video / Image | Optional if the text is not blank             |
| text         | Status Text                       | Optional if media or media\_code is not blank |

### Endpoint (Only POST Method)

```
https://pickyassist.com/app/api/v2/wa_status
```

### Sample Request 

```
{
	"token": "c81f742bea5e68a5213ec1afcc03a6a3d3b",
	"application": 10,
	"media": "https://pickyassist.com/img/gateway/gate_thumb.png",
	"text" : "New Product Released, For More Details https://pickyassist.com"
}

```

### Response

```
{
   "status":100,
   "push_id":"28896023",
   "message":"Success",
   "data":[
      {
         "msg_id":"33974091",
         "number":"status@broadcast",
         "credit":"0.005"
      }
   ]
}
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.pickyassist.com/api-documentation-v2/whatsapp-settings-apis/whatsapp-status-update.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.