Direct answer
Docketwise and INSZoom each document a REST API that a firm's own developer can build against. eimmigration offers two routes: its professional services team builds custom integrations, and it shares its API documentation with firms that would sooner build their own. Docketwise and CampLegal also connect to Zapier, which handles simpler automations without a developer.
Suppose a firm sends a monthly newsletter from an email marketing tool, and its case system has no ready-made connector for that tool. Today a legal assistant copies each new client's name and email address into the mailing list by hand. The firm wants a new client record to add that person to the list automatically.
The firm's developer or a contractor can write a small program against the case system's API that reads new clients and sends them to the mailing tool. The vendor's staff can build the connection as a paid service once the firm describes the result it wants. Or someone in the office can link the two apps on Zapier's site, with no code, by picking an event in one and an action in the other.
Each route depends on what both products expose. The case system has to make new clients available, and the mailing tool has to accept a new subscriber from outside. Check both ends before choosing, and decide who will maintain the connection when either product changes.
Docketwise's developer page describes a REST API that returns JSON, and the API documentation is public. A developer can read it before the firm commits to anything. Its menu lists contacts, matters, documents, notes, invoices, and charges among the resources. A firm asks for access through its customer success manager or Docketwise support, and its program then connects through OAuth 2.0. The developer page also invites software makers to submit an app for approval and a listing in Docketwise's app directory.
Mitratech describes INSZoom's API in its Zoom APIs help article. The examples there come from corporate immigration. An employer's HR system, such as Workday, sends employee and employment data into INSZoom and reads immigration status and case status back out. A staffing system creates or updates cases. A firm administrator requests the API by subscribing under Integrations on the subscription page, and Mitratech then contacts the administrator about what the firm needs.
For the newsletter example, a developer would begin by reading the contacts resource in Docketwise's documentation, or the client endpoints in INSZoom's list, to see whether new clients can be retrieved with the fields the mailing list needs.
eimmigration's integrations page closes with an offer to firms that don't find their tool among the listed connectors. The professional services team will build the integration, and a firm that prefers to build can ask eimmigration to send the API documentation to its developers.
The training and support page lists integrations among the professional services a customer can hire, next to custom development of forms, intakes, and reports. So the vendor-built route is a scoped project carried out by eimmigration's staff. For the firm in our example, the work begins as a written request that says which fields go to the mailing tool and what should happen when a client asks to be taken off the list.
eimmigration's pricing page lists API access under the Complete plan, with a footnote that limits it to accounts with 10 or more users. A 15-person firm on Complete with a developer available can request the documentation and study whether the newsletter connection is buildable. A six-person firm should ask the services team whether it will take the project on, and for a scope and a quote if it will.
Because API access is tied to a plan here, read it beside the other things the plan decides. WhatIsBest's comparison of immigration law software for US law firms covers eimmigration, Docketwise, and INSZoom on forms, filing, and storage by plan and edition.
Docketwise's Zapier help article lists what an automation can do with it. A contact being created or updated in Docketwise can start one, and the name and email address on that contact can be passed to another app. In the other direction, an event in another app can create or update a Docketwise contact. For the newsletter example, that is the Docketwise half. The firm still has to confirm that its mailing tool's entry in Zapier offers an action that adds a subscriber.
Every trigger and action in the article concerns a contact, so a firm planning an automation around matters should read Docketwise's current entry in Zapier before designing it.
CampLegal's pricing page lists Zapier webhooks on its Pro plan, and its integrations page describes connecting to other apps through Zapier without code. The examples it gives include sending an intake questionnaire when a contract is signed and pushing case data to another system. Before building on either example, open CampLegal's entry in Zapier and read which events and actions it offers.
Docketwise says it is still expanding its API, and Mitratech says it adds INSZoom endpoints as business needs come up. Before work starts, ask the vendor for the current resource list and set it beside the fields the firm wants to move.
Once a connection exists, test it with one made-up client whose every field is filled in. AnswerStack's answer on using Clio in place of specialized immigration software runs that kind of test on the Clio and Docketwise integration, where the open questions are which fields arrive and what happens when a record is edited afterward. Create the same client a second time as well. If the mailing list now holds that person twice, the integration needs a matching rule before it goes live.