Tells the external provider to stop delivering to the webhook URL Fruxon registered for this config — the un-install counterpart to `:applyWebhookToProvider`.
Lets an operator wind a channel down without leaving Fruxon to clear the webhook in BotFather / the provider hub. Providers with a programmatic deregistration API (Telegram `deleteWebhook` today) get a single-click disconnect; providers without one return 400 and the FE hides the affordance, exactly like the installer/inspector. No request body — removal needs no URL; it clears whatever the provider currently has registered for this config's credentials. This only stops the provider from sending; it does not delete Fruxon's webhook key (rotate/regenerate for that) or any trigger wiring. Returns 200 with `removed=false` + `errorMessage` when the provider rejects (auth failure, rate limit, network error) — the FE surfaces the message inline.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The integration ID.
The configuration ID.
uuidThe tenant identifier
Response Body
curl -X POST "https://api.fruxon.com/v1/tenants/string/integrations/string/configs/497f6eca-6276-4993-bfeb-53cbbbba6f08:removeWebhookFromProvider"{
"removed": false,
"providerResponse": "string",
"errorMessage": "string"
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Refreshes the cached bot identity for this configuration.
Calls the per-provider `IBotIdentityResolver` (Telegram `getMe`, Slack `auth.test`) and persists the resolved handle / display name / provider id onto the config. Drives the participant dialog's empty-state hint ("Send a message to @your_bot to populate suggestions"). Returns 200 with the resolved identity when the resolver could talk to the provider, 200 with the previously stored identity (or null) when credentials aren't connected yet — never 500 for a steady-state miss. Integrations without a resolver (Teams, Twilio, Dialog360 today) return 200 with null.
Restores a soft-deleted configuration.
Clears the soft-delete marker, re-enabling the credential for resolution — the escape hatch for a historical revision (or a revert to one) that still pins a config deleted under the sever semantics. Rejected with 400 if the config isn't currently soft-deleted. See `docs/design/integration-config-deletion-lifecycle.md`.