FruxonDocs
IntegrationsConfigs

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`.

POST
/v1/tenants/{tenant}/integrations/{integration}/configs/{config}:restore

Authorization

Bearer
AuthorizationBearer <token>

JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.

In: header

Path Parameters

config*string

The configuration ID.

Formatuuid
tenant*string

The tenant identifier

integration*string

The integration identifier

Response Body

curl -X POST "https://api.fruxon.com/v1/tenants/string/integrations/string/configs/497f6eca-6276-4993-bfeb-53cbbbba6f08:restore"
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}
Empty
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}

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.

Lists all revisions for a configuration.

Returns every published revision ever created for the config, ordered as stored (filter or sort client-side by `Version` for chronological order). Compare entries against the config's `PublishedRevisionId` to identify the currently active one; older revisions are retained for rollback via `:rollback`.