Integrations

Disconnect the key owner's Clio Manage · 0 credits

Disconnects Clio: asks Clio to revoke the stored token (POST /oauth/deauthorize on the firm's own regional instance) and then deletes the USER'S OWN dms_connections row, leaving a deletion tombstone. Returns { ok, deleted, revoked } and no token. revoked is what Clio ANSWERED, not the fact that we called: false means the revocation is unconfirmed and the firm should also remove the app from within Clio Manage; null means no revocation was attempted (no usable token). Thin loopback to /api/dms/clio/disconnect. No charge. Scope: mcp | *. API-only (side effect, no MCP tool). NOTE: connecting Clio is browser-only — it needs the consent screen plus a session that matches the signed state, and the firm's REGION (us|eu|ca|au), because Clio runs separate instances and a token issued in one is not valid against another.

post/api/v1/dms/clio/disconnect

Request

  • Base URL: https://legal.nexusquantum.legal
  • URL: https://legal.nexusquantum.legal/api/v1/dms/clio/disconnect
  • Auth: HTTP bearer

Response

{ ok, deleted, revoked }

object required

Changes

No recorded changes to this operation across all 1 revision of this API.