Hi Connie,

One example is let's say you have images and metadata stored within Laserfiche.

In another system, you have records that sometimes correspond to those images.

Maybe you want this system to have a button that opens up a customized display of the images and metadata stored within laserfiche, without using what's readily available through parametrized weblink URLs. 

This API would enable someone to code a webpage which can consume and display information from Laserfiche (the image and select metadata) in just the exact way your users of this non-Laserfiche system would prefer. (Yes this would typically be done by a VAR or someone with the ability to program.)

An API is a way to make common functions of an application, consumable by others via web programming in a safe, easy, and most critically, vendor supported, way. 

The link Cosette posted to the Developer Center is filled with instructions and examples on how to make use of it.
https://developer.laserfiche.com/guides/guide_getting-started.html

Hope this helps! Cheers

Hi Luke, 

The API product manager told me he'll be sure to follow up on that question tomorrow. 

Thanks, 

Cosette

Hi Farid,

The Laserfiche API is included to all Laserfiche 11 systems, although is its own download package as Pieter linked above. It will follow the same requirements as the Laserfiche SDK for licensed connections. 

Hi, the Laserfiche API Server does not need to be installed on the same server as the Laserfiche Server.

One of the configuration steps for the Laserfiche API Server is to set the fully qualified domain name of your Laserfiche Server in your network (step 3 under the installation configuration guide https://developer.laserfiche.com/api/server/index.html#installation-configuration )