Delete an integration
Disconnects the integration. If it holds OAuth tokens and the provider publishes a revocation
endpoint, Jelliu first asks the provider to revoke the grant (best effort: a failure is logged and
the delete continues). Then the integration is soft-deleted and, in the same write, its
credentials and both OAuth tokens are wiped. It disappears from every read, and the provider slot
is freed for a new POST /api/integrations or OAuth connect.
Side effects. Calls the provider’s revocation endpoint; stops the inbound webhook URL (pushes
are answered 401); writes an audit entry (action delete, resource integration).
Idempotency. Safe to retry: a repeat returns 404 because the integration is already deleted.
Webhook events. audit.log_recorded for webhooks subscribed to it. See Webhooks.
Access
- Required scope:
full. Humans need theadminorownerrole. - Rate limit: General API (120–600 requests/min per workspace by plan) plus the configuration-mutation limiter — 10 requests/min per workspace. See Rate limits.
- Plan: Available on every plan.
Authentication
Workspace API key: jl_ followed by 64 lowercase hex characters, created by the workspace owner in the
dashboard (Settings → API Keys) and sent as Authorization: Bearer jl_.... The plaintext is shown once,
at creation; Jelliu stores only a SHA-256 hash. A workspace can hold up to 25 active keys.
Operations restricted to admins or owners reject keys without the full scope with 403, and say so in
their description. No key, whatever its scope, can mint or revoke API keys or rotate a webhook secret —
that requires a signed-in owner session. A revoked key stops authenticating within about 10 seconds.
See Authentication.
Path parameters
Integration to delete. A value that is not a UUID is rejected with 400.