Update Telegram integration

Update the Telegram integration. Omitted fields keep their current value; threadId and chatLabel accept null to clear them.

patch/telegram-integration/project/{projectId}

Path parameters

projectIdstring required

botTokenstring

chatIdstring

threadIdnumber nullable

chatLabelstring nullable

isActiveboolean

The updated integration

idstring required

projectIdstring required

chatIdstring required

The Telegram chat, group, or channel messages are sent to.

threadIdnumber nullable required

Forum topic id, when the target group uses topics.

chatLabelstring nullable required

A human-readable name for the chat, shown in the UI.

botTokenConfiguredboolean required

maskedBotTokenstring required

isActiveboolean nullable required

createdAtstring date-time required

updatedAtstring date-time required

Changed in 2 of the 23 revisions of this API.35

Aug 24, 202608bbb5bedb5d34See the full diff
- ▲
  the request property chatLabel became not nullable
  request-property-became-not-nullable
- ▲
  the request property threadId became not nullable
  request-property-became-not-nullable
- ▲
  the response's body became nullable
  response-body-became-nullable
- ○
  added the non-success response with the status 400
  response-non-success-status-added
- ○
  added the non-success response with the status 401
  response-non-success-status-added
- ○
  added the non-success response with the status 403
  response-non-success-status-added
- ○
  added the non-success response with the status 404
  response-non-success-status-added
This revision also has 3 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Jul 11, 202632cece1ebe431See the full diff
- ○
  endpoint added
  endpoint-added