curl --request DELETE \
--url https://api.backside.app/api/v1/me/integrations/{kind}/{id} \
--header 'Authorization: Bearer <token>'integration_key — looks up the row’s provider by id (tenant-
scoped), then calls revoke_integration_key(pool, tenant_id, provider). The underlying helper is keyed by provider (one
active key per provider per tenant); the public URL is
:id-keyed for API consistency.oauth_connection — calls revoke_oauth_connection(pool, tenant_id, id).agent_config_byok — looks up the row’s agent_blueprint by
id (tenant-scoped), then calls revoke_byok(pool, tenant_id, &agent_blueprint). Same per-id → per-blueprint rewrite as the
integration-key case.On success, an activity_log entry is written (category = "integration", severity = "warning") so operators have a per-
revocation audit trail in the same stream as DEV-20/22 operator
events. Revocation is considered a “worth your attention” event:
not an error, but not routine enough to be silent.
curl --request DELETE \
--url https://api.backside.app/api/v1/me/integrations/{kind}/{id} \
--header 'Authorization: Bearer <token>'Was this page helpful?