Meet Caddi in personADVISE AIOct 20–22AI for Mid-Sized LawNov 5Legal InnovatorsNov 17–18
LawPay API

Connect LawPay without building on its API

LawPay has a REST API. LawPay merchants get their own API keys in the Developers settings (Admins, Developers or Merchant Owners only); partner apps use OAuth, and LawPay asks partners to contact it. If you're reading the docs because you need LawPay to talk to the rest of your stack, Caddi does that without you writing or maintaining integration code: you show it the job once, and it runs it across LawPay and your other tools.

  • APIREST (JSON)
  • AuthHTTP Basic auth with secret key fo
  • AccessSelf-serve for merchants
The LawPay API

What the LawPay API gives you

Type
REST (JSON)
Authentication
HTTP Basic auth with secret key for payment calls; OAuth 2.0 for partner apps that connect merchant accounts
Who can get access
LawPay merchants get their own API keys in the Developers settings (Admins, Developers or Merchant Owners only); partner apps use OAuth, and LawPay asks partners to contact it.
What it covers
Payment transactions (charges, refunds, voids), saved payment methods, merchant and ACH accounts, recurring charges, and signatures.

Official docs: developers.8am.com. Checked September 2026. Vendors change access terms, so confirm with LawPay before you build.

Build or have it run

Building on the LawPay API vs. having Caddi run it

The jobBuild it on the APIWith Caddi
Getting accessRegister an app, get LawPay credentials, and manage tokens and refreshes.Connect your LawPay account once. Caddi holds the connection.
Writing the integrationA developer maps fields, handles pagination, retries and rate limits, and writes the sync.You show Caddi the LawPay task the way you'd train a new hire. It writes verified code for it.
Steps the API doesn't coverScreens with no endpoint stay manual, or need a separate RPA tool.Caddi uses a secure, audited browser session where there's no API, in the same automation.
The other systems in the loopEach extra tool is another API, another set of credentials, another integration to own.One automation runs across all the tools the job touches.
Keeping it runningSomeone owns the code when the API version, fields or your process change.Every automation is reviewed before it runs in production, and every run is logged.

Building on the API is the right call when you have engineers and the integration is your product. When the goal is getting LawPay work off someone's desk, the build is the slow part.

What teams connect

What teams usually want the LawPay API for

  • Collection Payment Receipts

    Caddi identifies today's collection payments, resends receipts to the right recipients, and updates the corresponding case record and email tagging.

  • Matter-level reconciliation

    Caddi reads the daily LawPay export, matches each line to the right matter in Clio, and writes the reconciled record back.

  • Trust deposit logging

    Caddi captures trust deposit details from LawPay and posts the matching entries to the firm's trust ledger and matter record.

Everything Caddi does with LawPay.

LawPay API questions

Does LawPay have an API?

Yes. LawPay has a REST API, authenticated with HTTP Basic auth with secret key for payment calls; OAuth 2.0 for partner apps that connect merchant accounts. The official documentation is at https://developers.8am.com/.

How do I get access to the LawPay API?

LawPay merchants get their own API keys in the Developers settings (Admins, Developers or Merchant Owners only); partner apps use OAuth, and LawPay asks partners to contact it.

Can I connect LawPay to my other tools without writing code against its API?

Yes. With Caddi you show the LawPay task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across LawPay and the other tools the job touches. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.

Do I need a developer to automate LawPay with Caddi?

No. There is no integration code for you to write or maintain. Every automation Caddi builds for LawPay is reviewed before it runs in production, and every run is logged.

Connect LawPay without the build.

Drop your work email and pick a time. We'll show you Caddi running your LawPay workflow end to end.