Authenticate to the Clio Manage API via OAuth 2.0 and register a webhook to receive real-time matter update events
domain: clio.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register an application in the Clio Developer portal to obtain a client ID and secret
Implement the OAuth 2.0 authorization code grant: redirect the user to Clio's authorization screen, then exchange the returned code for an access token
Confirm your application holds the OAuth scope corresponding to the matter model before attempting to create a webhook for matter events
Create a webhook record specifying the target URL, the matter model, an events list, and (optionally) an expires_at value
On each incoming webhook POST, compute the HMAC-SHA256 signature using your shared secret and compare it against the X-Hook-Signature header before trusting the payload
Track each webhook's expiration and recreate or renew it before it lapses
Known gotchas
Webhooks expire automatically — after 3 days by default if no expires_at is supplied, with a maximum lifetime of 31 days — so subscriptions require proactive renewal, not one-time setup
Creating or updating a webhook for a given model requires your app to already hold the OAuth scope for that specific model (e.g., the document scope for folder webhooks), not just a generic webhook scope
Every webhook payload is HMAC-signed via the X-Hook-Signature header; skipping signature verification means spoofed requests to your endpoint can't be distinguished from genuine Clio events
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?