Providers Overview

Every provider goes through the same adapter contract, so the API you write against does not change. What differs is what each provider can actually do—how its hierarchy is shaped, how it reports changes, and how hard you can push it. Build against the matrix, not against one provider’s behavior.

Capability matrix

	Clio Manage	Google Drive	Box
`provider` value	`clio`	`gdrive`	`box`
Import	Yes	Yes	Yes
Export	Yes	Yes	Yes
Top-level containers	Matters	My Drive, shared drives	All Files
Browse depth	Folder	Container → folder	Folder
Change detection	Updated-since	Native delta	User events + reconciliation
Selectable collections	Documents, communications, tasks	—	Documents
Default scope tier	`clio.us`	`drive`	`box.readwrite`
Availability	Generally available	Requires enablement	Preview validation

Rate budgets

Each provider has a request budget that interactive browsing and background runs share. A large sync in progress will make browsing feel slower for the same account.

Provider	Requests/min	Concurrent transfers
Google Drive	12,000	4
Clio Manage	45	4
Box	900	4

Clio’s budget is tight. If you are building a Clio integration, read its guide before designing your browse UI.

Token refresh behavior

You never handle tokens, but refresh behavior affects how often users are asked to reconnect. Clio and Google Drive issue long-lived refresh tokens. Box refresh tokens rotate after each use and expire after 60 days without use. Handle connection.reauth_required for every provider.

Change detection and what it costs

Strategy	Provider	Behavior
Native delta	Google Drive	The provider reports what changed. Incremental runs are cheap.
User events	Box	Current metadata and ancestry determine subtree membership; structural changes trigger reconciliation.
Updated-since	Clio Manage	Queries by modification time. Efficient, but deletions are detected on the daily full reconcile.

No provider currently drives synced links through push notifications. Synced links are kept current by a polling sweep—treat “synced” as current within the hour, not real time.

Discovering availability at runtime

Do not hardcode the provider list. GET /connectors/v1/connections returns a providers array describing what is live for the calling organization:

Response fragment

{
  "providers": [
    {
      "id": "clio",
      "scope_tier": "clio.us",
      "supports_export": true,
      "resource_types": ["documents", "communications", "tasks"]
    },
    { "id": "gdrive", "scope_tier": "drive", "supports_export": true, "resource_types": [] }
  ]
}

Drive your UI from this. A provider gated for the organization returns 403 connector_scope_not_enabled at connect time—better to not show the button.

Get Started

Platform

Resources

Providers Overview

Capability matrix

Rate budgets

Token refresh behavior

Change detection and what it costs

Discovering availability at runtime

Guides

Box

Clio Manage

Google Drive

​Capability matrix

​Rate budgets

​Token refresh behavior

​Change detection and what it costs

​Discovering availability at runtime

​Guides

Box

Clio Manage

Google Drive

Capability matrix

Rate budgets

Token refresh behavior

Change detection and what it costs

Discovering availability at runtime

Guides