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

# Update Advanced Webhook Config

Use this API to update the advanced webhook configuration for a workspace. At least one of `isEnabled`, `encryptData`, `encodeData`, `publicKey` or `enableDataProtection` must be provided.

> [!NOTE]
>
> This endpoint uses **API-key-level auth**: pass `x-velt-api-key` and `x-velt-auth-token` as headers. You can obtain these from the [Get Auth Tokens](https://velt.dev/docs/api-reference/rest-apis/v2/workspace/authtokens-get.md) endpoint.

> [!NOTE]
>
> This endpoint is for **Advanced Webhooks**. For Basic Webhooks, use [Update Webhook Config](https://velt.dev/docs/api-reference/rest-apis/v2/workspace/webhookconfig-update.md).

> [!NOTE]
>
> **First enable.** If advanced webhooks have never been configured for the workspace, the first request must include `isEnabled: true` — this provisions the underlying webhook application for your workspace. Sending only other fields before the first enable returns a `FAILED_PRECONDITION` error. After the first enable, you can manage delivery endpoints via the [endpoint management APIs](https://velt.dev/docs/api-reference/rest-apis/v2/workspace/advancedwebhook-endpoints-create.md).

> [!NOTE]
>
> **Partial update.** Only the fields you send are changed; all other stored values are preserved. The response `data` echoes the latest post-write state — the same shape returned by [Get Advanced Webhook Config](https://velt.dev/docs/api-reference/rest-apis/v2/workspace/advancedwebhookconfig-get.md).

# Endpoint

`POST https://api.velt.dev/v2/workspace/advancedwebhookconfig/update`

# Headers

**x-velt-api-key** `string` *required*

Your API key.

**x-velt-auth-token** `string` *required*

Your [Auth Token](https://velt.dev/docs/security/auth-tokens.md).

# Body

#### Params

**data** `object` *required*

**properties**

**isEnabled** `boolean`

Whether to enable advanced webhooks. Must be `true` on the very first configuration request.

**encryptData** `boolean`

Whether to encrypt the webhook payload.

**encodeData** `boolean`

Whether to base64 encode the webhook payload.

**publicKey** `string`

Public key used for payload encryption.

**enableDataProtection** `boolean`

Whether to enable data protection for webhook payloads.

# Example Request

```JSON theme={null}
{
  "data": {
    "isEnabled": true,
    "encryptData": false,
    "encodeData": false
  }
}
```

# Example Response

#### Success Response

```JSON theme={null}
{
  "result": {
    "status": "success",
    "message": "Advanced webhook configuration updated successfully.",
    "data": {
      "isEnabled": true,
      "encryptData": false,
      "encodeData": false,
      "publicKey": "",
      "enableDataProtection": false
    }
  }
}
```

#### Failure Response

```JSON theme={null}
{
  "error": {
    "status": "INVALID_ARGUMENT",
    "message": "At least one of isEnabled, encryptData, encodeData, publicKey or enableDataProtection must be provided."
  }
}
```

```js theme={null}
{
  "result": {
    "status": "success",
    "message": "Advanced webhook configuration updated successfully.",
    "data": {
      "isEnabled": true,
      "encryptData": false,
      "encodeData": false,
      "publicKey": "",
      "enableDataProtection": false
    }
  }
}
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.