Laserfiche APIConnect Laserfiche without building on its API
Laserfiche has a REST API. Laserfiche customers only: Cloud accounts register apps in the Developer Console, and self-hosted needs Laserfiche API Server 11+ (the SDK is licensed separately). If you're reading the docs because you need Laserfiche 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 Laserfiche and your other tools.
- APIREST (JSON)
- AuthOAuth 2.0 for Cloud
- AccessSelf-serve for customers
What the Laserfiche API gives you
- Type
- REST (JSON)
- Authentication
- OAuth 2.0 for Cloud (HTTP Basic for OData only); token endpoint with credentials for self-hosted
- Who can get access
- Laserfiche customers only: Cloud accounts register apps in the Developer Console, and self-hosted needs Laserfiche API Server 11+ (the SDK is licensed separately).
- What it covers
- Repositories, documents, folders, metadata/fields, pages, import/export, lookup tables, and collections.
- Limits
- Cloud: 100 calls/min per account for general APIs, a shared 100/min for import/export, and tighter limits for Table API replace calls.
- Worth knowing
- Collections and OData APIs are not available for self-hosted deployments.
Official docs: developer.laserfiche.com. Checked September 2026. Vendors change access terms, so confirm with Laserfiche before you build.
Building on the Laserfiche API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Laserfiche credentials, and manage tokens and refreshes. | Connect your Laserfiche account once. Caddi holds the connection. |
| Writing the integration | A developer maps fields, handles pagination, retries and rate limits, and writes the sync. | You show Caddi the Laserfiche task the way you'd train a new hire. It writes verified code for it. |
| Steps the API doesn't cover | Screens 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 loop | Each 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 running | Someone 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 Laserfiche work off someone's desk, the build is the slow part.
What teams usually want the Laserfiche API for
Model Form Filing
Caddi files and classifies client investment model selection forms in the correct intake folder, reducing manual document filing for advisor teams.
Household Review Report Filing
Caddi generates household review meeting report PDFs and files them with the correct metadata, reducing manual report prep and archiving for advisor teams.
Signed Model Form Archiving
Caddi collects signed model selection forms and archives the final PDFs with the right metadata, reducing manual follow-up and filing for advisor teams.
Financial Report Archiving
Caddi generates client financial report PDFs and archives them with the correct template and metadata, reducing manual report handling for financial planning teams.
Laserfiche API questions
Does Laserfiche have an API?
Yes. Laserfiche has a REST API, authenticated with OAuth 2.0 for Cloud (HTTP Basic for OData only); token endpoint with credentials for self-hosted. The official documentation is at https://developer.laserfiche.com/.
How do I get access to the Laserfiche API?
Laserfiche customers only: Cloud accounts register apps in the Developer Console, and self-hosted needs Laserfiche API Server 11+ (the SDK is licensed separately).
Does the Laserfiche API have rate limits?
Cloud: 100 calls/min per account for general APIs, a shared 100/min for import/export, and tighter limits for Table API replace calls.
Can I connect Laserfiche to my other tools without writing code against its API?
Yes. With Caddi you show the Laserfiche task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Laserfiche 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 Laserfiche with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Laserfiche is reviewed before it runs in production, and every run is logged.
Connect Laserfiche without the build.
Drop your work email and pick a time. We'll show you Caddi running your Laserfiche workflow end to end.