> 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/project-management-api/set-update-webhook.md).

# Set / Update Webhook

{% hint style="danger" %}

## Project Management API is disabled from Feb 1st, 2023 onwards, so any request made to this en point will fail

{% endhint %}

This API allows you to set / update webhooks against each project

##  Update Webhook

<mark style="color:green;">`POST`</mark> `https://pickyassist.com/app/api/v2/pm/update-webhook`

This API allows you to Update Webhook

#### Request Body

| Name                  | Type   | Description                                                                                                                                          |
| --------------------- | ------ | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| token                 | string | Your Master API Token for authentication                                                                                                             |
| project\_id           | number | Project Id in which the webhook need to configured                                                                                                   |
| global\_webhook       | string | <p>Pass the Webhook URL which needs to be configured for Global Webhook<br><br>Please note if you pass blank value then webhook will be removed </p> |
| event\_webhook        | string | <p>Pass the Webhook URL which needs to be configured for Event Wehook<br><br>Please note if you pass blank value then webhook will be removed  </p>  |
| smart\_reply\_webhook | string | <p>Pass the Webhook URL which needs to be configured fro Smart Replies <br><br>Please note if you pass blank value then webhook will be removed</p>  |

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

```
{
   "status":100,
   "message":"Success"
}
```

{% endtab %}
{% endtabs %}

## Response Variables&#x20;

| Variable | Type    | Description                                                                                                                                                                               |
| -------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| status   | numeric | <p>Status of the Request </p><p></p><p>100 = Sucess</p><p></p><p>Refer <a href="/api-documentation-v2/references/status-and-error-codes.md">Error Codes</a> for complete Status Codes</p> |
| message  | string  | Error or detailed response Message details                                                                                                                                                |

## Sample Request Body JSON

```javascript
{
   "token":"343434sdfdfdf",
   "project_id":733714,
   "global_webhook":"https://pickyassist.com/beta/test_webhook.php",
   "event_webhook":"https://pickyassist.com/beta/test_webhook.php",
   "smart_reply_webhook":"https://pickyassist.com/beta/test_webhook.php"
}
```

## Sample Response

```javascript
{
   "status":100,
   "message":"Success"
}
```


---

# 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://help.pickyassist.com/api-documentation-v2/project-management-api/set-update-webhook.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.