---
title: "Configure a chat integration webhook"
method: POST
path: "/v1/integrations/{integrationIdentifier}/webhook/configure"
tags: ["Integrations"]
---

# Configure a chat integration webhook

`POST /v1/integrations/{integrationIdentifier}/webhook/configure`

## Request

- Base URL: `https://api.notifly.io`
- URL: `https://api.notifly.io/v1/integrations/{integrationIdentifier}/webhook/configure`
- Auth: API key in header `Authorization`

Registers the Notifly webhook URL with the chat provider for the specified integration. Telegram is the only supported provider initially.

## Path parameters

- `integrationIdentifier` string, required

## Response `200`

OK

- object
  - `data` ConfigureTelegramWebhookResponseDto
    - `webhookUrl` string, required: URL Notifly registered with Telegram for incoming updates
    - `configuredAt` string, required: ISO-8601 timestamp the webhook was configured at
    - `botUsername` string, required: Resolved bot username from getMe

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `403`: Forbidden
- `404`: Not Found
- `405`: Method Not Allowed
- `409`: Conflict
- `413`: Payload Too Large
- `414`: URI Too Long
- `415`: Unsupported Media Type
- `422`: Unprocessable Entity
- `429`: The client has sent too many requests in a given amount of time.
- `500`: Internal Server Error
- `503`: The server is currently unable to handle the request due to a temporary overload or scheduled maintenance, which will likely be alleviated after some delay.

---

[API](https://skmtc.dev/notifly/apis/notifly-api.md) · [All operations](https://skmtc.dev/notifly/apis/notifly-api/llms.txt) · [OpenAPI document](https://skmtc.dev/notifly/apis/notifly-api/revisions/af909b9e1e57?raw)