Reject managed Telegram bot rename | Runtype Documentation

Reject a renamed managed Telegram bot, tearing down its integration record and credentials so the user can retry.

AuthorizationBearer

API key or Clerk session token

requestIdstringRequired

Rename rejected

okboolean

outcomestring

resultany

401

Unauthorized Error

403

Forbidden Error

404

Not Found Error

409

Conflict Error

$	curl -X POST https://api.runtype.com/v1/integrations/telegram/managed/requestId/reject-rename \
>	-H "Authorization: <apiKey>" \
>	-H "Content-Type: application/json" \
>	-d '{}'

$	curl -X POST https://api.runtype.com/v1/integrations/telegram/managed/requestId/reject-rename \
>	-H "Authorization: <apiKey>" \
>	-H "Content-Type: application/json" \
>	-d '{}'

1	{
2	"ok": true,
3	"outcome": "Rename request successfully rejected and integration credentials removed"
4	}