Legal Workflow StudioA site of The Goodstack Company Assess a handoff

Integration guide

Legal software integration limits: access, queues and retries

A rate limit tells you how requests are counted. A useful integration assessment also names the permitted operation, the approval it waits for, the queue owner and what happens when a write has an unknown result.

The number that decides how an integration behaves

A rate limit is one capacity constraint. It does not establish whether an integration can read the required record, perform an authorized write or recover interrupted work. Start with the exact operation you need, then check its access, request budget and failure path.

This guide uses current Clio documentation to explain the difference between a token limit and an application limit. The checklist and example are our proposed engineering method. They help a buyer ask for evidence from an existing provider or a custom developer.

We have not delivered a system for a law firm. This is an administrative integration guide; your responsible attorney defines the firm's conflict, acceptance, engagement and access requirements. No practitioner has reviewed the synthetic example below.

Two products, two rulebooks

Clio's product API guide, checked October 28, 2026, currently directs Manage integrations to a Manage application and Grow integrations to a Clio Platform application. Connecting both requires separate applications and separate user OAuth authorizations. The page describes future consolidation; that plan does not establish present access.

APIDocumented rate-limit scope, checked October 28, 2026
Clio Manage API v4Default 50 requests per minute during peak hours, counted per access token. US/Canada peak hours are 04:00–19:00 Pacific, Monday–Friday. Off-peak limits increase by an amount that can differ by region. Some endpoints have their own limits.
Clio Platform APIDefault 3 requests per second, shared by all users of one OAuth application. Regional limits are separate. The page recommends request queues and exponential backoff for rate-limit responses.

Manage documents X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset response headers, plus Retry-After on a rate-limit 429. Use the returned values and the operation's current documentation: Manage says limits can change without notice. Both linked rate-limit pages currently say custom increases are unavailable. These are dated published defaults, not a completion-time promise.

Access needs its own check. Manage's permissions documentation, checked October 28, 2026, distinguishes the application's OAuth permissions from the user's role permissions. It advises requesting the smallest necessary set. Adding an application permission after authorization requires the affected user to reauthorize; refreshing a token alone does not add that permission. Some associated data can be redacted because of access or user permissions.

Record the product, region, operation and required fields before drawing a conclusion about access. A working login or one successful read does not demonstrate that a different write is permitted. Check the chosen endpoint and the actual authorized role. Do not treat an unknown operation as an unavailable vendor feature.

Why per-application matters more than the number

The counting boundary matters alongside the number. Manage documents a limit for requests using the same access token. That is narrower than saying every firm has isolated capacity: the documentation does not prove how your provider allocates tokens, workers or other resources.

For Platform, users of the same OAuth application in one region share its quota. That does not mean every Clio customer shares one allowance. Ask the provider which application serves your connection and how it schedules competing work. A custom build and a packaged integration both need an answer.

Make the workload estimate explicit. Count the reads, writes, lookups, paginated requests and retries needed for one transfer. Then consider bursts, existing backlog and other work using the same quota. A request allowance alone cannot tell you how many complete matters a connection will finish in a minute.

An event-driven design may reduce unnecessary reads where the required events are available. Polling can still be appropriate for a supported operation. Ask for the actual event or polling plan, its request cost and how it recovers missed work. Scheduling batch work outside Manage's peak hours may help a measured workload; it does not increase Platform's documented per-application allowance.

What this looks like on a real morning

Synthetic demonstration: invented records. This extends the scorecard's Q-104 handoff into an operation-level test plan. No real firm or client is shown. No connector or API request was executed for this example, and no practitioner has reviewed it. Every test below starts as not run.

Copy an operation evidence sheet

Use a separate sheet for each operation, such as reading an approved inquiry, looking up a destination record or creating a matter. Keep secrets and confidential records out of the sheet; use test references and restricted evidence storage where needed.

FieldEvidence to record
Operation and ownerSource record, destination operation, authoritative system and the staff member who owns an unresolved transfer.
Product and accessAPI, version, region, endpoint/method, required fields, OAuth permissions, authorized role and dated documentation. Record each as documented, tested or unknown.
Approval and triggerRequired human decision, where its evidence lives, permitted event or polling method, and what blocks dispatch when approval is missing.
Request budgetCalls per transfer, paging, retries, shared quota, observed response headers and maximum acceptable queue age agreed with operations.
Result and reconciliationExpected response, destination identifier, lookup method, ambiguous-result state and who checks an uncertain write.
Duplicate preventionThe specific supported mechanism or integration design, its limits, and evidence from repeat, concurrent and interrupted attempts.
Recovery and costRetry limit, escalation, manual fallback, recovery owner, review time and recurring support responsibility. Separate measured work from estimates.

The draft Q-104 sheet proposes one authorized matter transfer after the firm's required human decisions and engagement conditions are recorded. Intake remains the source of the inquiry reference; the destination matter ID is recorded separately. The matter administrator owns uncertain transfers. Endpoint access, correlation lookup and duplicate prevention are unknown until documented and tested. Q-104 is a trace reference, not proof that an API enforces uniqueness.

Exercise the distinct failure paths

Use invented records in an isolated test setup. Record the input, application version, permissions, attempt ID, response or missing response, queue state, destination records and reviewer for each case. Do not include live credentials in the evidence.

  1. Required approval missing. Withhold the prerequisite decision for Q-104. Expected: no matter-create request; a visible pending item names the person responsible for the decision. A retry cannot supply approval.
  2. Recorded rate-limit response. Make the test service return 429 without creating a record. Expected: retain the work, pace retries according to the selected API's documented behavior and apply a bounded retry policy. Preserve the response and queue age. The Platform page recommends backoff; Manage documents Retry-After. Do not invent a Platform header from Manage's rulebook.
  3. Access failure. Return 401 for an invalid token, then separately 403 for insufficient permission. Expected: distinguish the failures, stop blind retries and route the item to the access owner. Refresh or reauthorization follows the approved access plan; extra permissions require a separate decision. Clio's Platform error table makes this distinction.
  4. Write accepted, response lost. Have the test destination create a record, then suppress the response. Expected: Q-104 enters an unknown-result queue. Look up the result using the documented correlation method and verify the intended record and permissions. If the result is absent, incomplete or ambiguous, keep it open for investigation. Do not infer that a timeout means no record was created.
  5. Repeat and simultaneous attempts. Replay Q-104, including two attempts that start together. Expected: the chosen duplicate-prevention design produces one intended destination matter and preserves an explanation of the other attempts. A lookup before creation alone can miss a race where both attempts see nothing. Do not claim a provider supports an idempotency key without endpoint-specific evidence.
  6. Backlog and operator recovery. Queue several invented transfers, stop dispatch and have the assigned operator reconcile pending and uncertain work. Expected: every item has a visible owner and outcome; none silently disappears or is marked complete without evidence. Record oldest queue age, actual recovery effort and unresolved cases before resuming.

Save failures and reruns as well as passes. A successful normal transfer does not clear a failed approval, access or duplicate-prevention test. If the evidence needed to judge a case is missing, keep its result inconclusive. Passing these selected cases covers those tested conditions; it does not establish all future workloads or failure behavior.

What to ask, and what a good answer sounds like

Ask for the operation sheet and the evidence behind each answer. A useful response names the scope, shows the result and marks what remains untested. Someone needing to investigate a detail is not itself evidence of a defective integration.

  • Which API and operation are involved? Look for product, region, permission and field coverage, including separate authorization where both Manage and Grow are involved.
  • Which workload shares this quota? Ask how interactive work and batch jobs are queued, what staff can see and when an overdue item is escalated.
  • What differs between a 429 and an unknown write result? Request separate demonstrations of pacing and reconciliation. Waiting before another request does not by itself prevent duplicate creation.
  • What prevents concurrent duplicates? Ask to see the actual mechanism and a repeat/concurrency test. Keep unknown endpoint behavior explicit.
  • Who handles the remaining work? Name the owner for token problems, denied access, ambiguous writes and manual recovery. Include review, correction and support effort when comparing options.

Compare configuration of the installed product, an existing connector and a scoped custom integration against the same operation and tests. Keeping the current system can be a useful outcome. If access or recovery remains unknown, the next deliverable is a bounded feasibility check with an owner and decision date. It is too early to price the unknown as a proven routine connection.

The honest position

The published limits apply to the API being used; a custom build does not erase them. The engineering choices are which operations to attempt, how to schedule them, what evidence to retain and who handles an unresolved result. An existing integration that demonstrates the required behavior may already meet the need.

Use the CRM, intake and practice-management comparison to decide which system owns each record. Use the intake workflow scorecard to identify the handoff worth investigating. This guide supplies the operation and recovery questions for that investigation.

We can map one administrative handoff around your existing systems. We are new to legal and have not delivered a law-firm system. For a first conversation, share the system names, the operation and its owner. Leave client records, credentials and confidential matter details out of the inquiry.

The linked Clio documentation was checked October 28, 2026. Capabilities and limits can change; recheck the relevant operation before implementation. Goodstack has no partnership or affiliation with Clio, and this guide is not endorsed by Clio.

Assess an integration handoff