FruxonDocs
IntegrationsCore

Deletes a custom integration and its tools.

Configs are not cascaded — they must be deleted explicitly first so agents pinned to a config don't get silently broken. System integrations cannot be deleted and return 404.

DELETE
/v1/tenants/{tenant}/integrations/{integration}

Authorization

Bearer
AuthorizationBearer <token>

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

In: header

Path Parameters

integration*string

The unique identifier of the integration.

tenant*string

The tenant identifier

Response Body

curl -X DELETE "https://api.fruxon.com/v1/tenants/string/integrations/string"
Empty
Empty
Empty
{
  "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
}

Consumes temporarily stored OAuth credentials from a completed application-level OAuth flow and creates an `IntegrationAuth` record bound to the specified integration config.

The credential key is returned to the frontend via the OAuth success redirect after the user completes authorization. The resulting connection is shared by every agent that references the target config. The credential key is single-use.

Lists the countries an integration's outbound traffic can be pinned to egress from.

Each entry is a country with a forward proxy provisioned, so an integration pinned to it has its API tool calls originate from a fixed, country-specific IP — for endpoints that allowlist callers by source IP. Use this to populate the egress-country picker when editing an integration config. The set is driven by deployed infrastructure, so it changes without a code release.