FruxonDocs
IntegrationsConfigs

Mints a short-lived, client-usable OAuth access token for this config so an in-browser SDK that requires the token directly (e.g

Available only for integrations that opt in via `Integration.AllowsClientOAuthToken` — a live token in the browser is usable outside Fruxon with the config's full scopes, so most integrations must never expose it. The token carries the config's scopes and self-expires on the provider's TTL. The underlying credential access is audited by the resolver; this adds a distinct browser-vend log signal. Returns 400 when the integration hasn't opted in, the config has no OAuth auth configured, the stored credentials can't be refreshed, or no account is connected yet.

POST
/v1/tenants/{tenant}/integrations/{integration}/configs/{config}/clientToken

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 integration ID.

config*string

The configuration ID.

Formatuuid
tenant*string

The tenant identifier

Request Body

Optional body carrying a use-case hint for the vend log signal.

useCase?string|null

Free-form hint describing why the client token is needed (audit / telemetry only).

[key: string]?never

Response Body

curl -X POST "https://api.fruxon.com/v1/tenants/string/integrations/string/configs/497f6eca-6276-4993-bfeb-53cbbbba6f08/clientToken" \  -H "Content-Type: application/json" \  -d '{}'
{
  "accessToken": "string",
  "expiresAt": 0
}
{
  "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
}

Registers the freshly-minted webhook URL with the external provider on the operator's behalf

Closes the gap where the operator otherwise has to paste the URL into BotFather / Slack app settings / Twilio console manually. Providers with a programmatic registration API (Telegram `setWebhook` today, more later) get a single-click install; providers without one (Slack Events API, Teams Bot Framework) return 400 and the FE renders manual instructions instead. The FE supplies the URL it just received from `:generateWebhookUrl` / `/webhook:rotate` via the request body — Fruxon doesn't store the plaintext key, so the round-trip through the operator's browser is the only way the BE can pass the full URL to the provider. Returns 200 with `applied=false` + `errorMessage` when the provider rejects (auth failure, malformed URL, rate limit) — the FE surfaces the message inline and offers the manual-install fallback.

Deletes a configuration.

Rejected with 400 if any agent's <em>current</em> revision (or a participant / active trigger) still references this config via `TenantConfigId` — use the `/usage` endpoint to check first. With no live references, the config is hard-deleted (along with its revision history) when nothing references it at all, or <em>soft-deleted</em> when only a historical agent revision still pins it — the row is retained (and the credential severed from live use) so a revert can `:restore` it. See `docs/design/integration-config-deletion-lifecycle.md`.