Reference · built on requestConnectorFiles, documents & spreadsheets

Laserfiche

Repository entries, documents, folders, and field metadata in Laserfiche Cloud through the Repository API.

Request accessPricing ↗

About

Laserfiche is a content and records management system. Its Repository API V2 reaches Laserfiche Cloud at api.laserfiche.com, api.laserfiche.ca, and api.eu.laserfiche.com, and Self-Hosted repositories on Laserfiche 11 or later through the Laserfiche API Server. Entries are documents, folders, shortcuts, and record series. Each entry can carry a template and field values. Copy, delete, and the async import, export, and search calls return a taskId you poll.

Through Fibric, an operator lists a folder, reads the fields on each entry, and proposes an import, a field update, or an export. You approve it. A receipt records what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Laserfiche and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Folder contents through GET /repository/v2/Repositories/{repositoryId}/Entries/{entryId}/Folder/Children, with $select, $orderby, $top, $skip, and up to 10 requested fields
  • Entries typed as Laserfiche.Repository.Document, Folder, Shortcut, or RecordSeries, with their templates and field values
  • Search results through POST Searches/SearchAsync with a searchCommand, then GET Searches/{taskId}/Results and per-row ContextHits
  • Task status through GET Repositories/{repositoryId}/Tasks?taskIds=, with percentComplete, startTime, lastUpdateTime, and errors
  • Field and template definitions, tags, and links defined in the repository
  • Exported document content as Edoc, Image, or Text through Export and ExportAsync, returned as a download link

Proposed actions

  • Target capability: propose an import through POST Entries/{parentEntryId}/Folder/Import with the name, templateName, fields, and tags shown first
  • Target capability: propose field values through PUT Entries/{entryId}/Fields, carrying every existing value so none is cleared
  • Target capability: propose an export of an entry's Edoc, Image, or Text part, with pageRange and audit reason
  • Target capability: propose a copy or a move of an entry, tracked as a task until it completes

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Chase the certificate before it expires

    The operator lists the vendor folder with the expiry field requested, finds certificates within the window you set, and proposes a request to the vendor for a fresh one.

    With COI Expiry

  • Check a contractor's credentials on file

    The operator searches the repository for the contractor's records, reads the field values on each entry, and proposes a hold on site access when a required document is missing or out of date.

    With Contractor Credentials

  • Assemble the audit record

    The operator exports the documents an auditor names, with an auditReasonId on each export, and proposes the bundle with its field values listed.

    With Audit Trail, Compliance Evidence

  • File a new account application

    The operator imports the signed application into the right folder with the template and fields set, and proposes the entry for review.

    With Account Application

Requirements

  • A Laserfiche Cloud account with a service principal created in Account Administration and a Service App registered in the Developer Console
  • An access key on that Service App; each Service App holds at most 2
  • Scopes granted to the app, repository.Read for reading and repository.Write where imports and field updates are approved
  • For Self-Hosted, Laserfiche 11 or later with the Laserfiche API Server installed and reachable
Authentication
OAuth 2.0 client_credentials from a Service App in the Laserfiche Developer Console: a JWT signed with the Access Key and Service Principal Key is exchanged at signin.laserfiche.com/oauth/token for a bearer token scoped to repository.Read or repository.Write.

Limits

  • Service App tokens carry no refresh token; a new token is requested when the old one expires
  • A simple import accepts files up to 100 MB; larger files go through CreateMultipartUploadUrls and ImportUploadedParts, up to 64 GB
  • A synchronous Export fails if it runs longer than 60 seconds; use ExportAsync and poll the task instead
  • Task IDs expire 15 minutes after the operation completes, and in Cloud only a limited number of searches can be active per session

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Laserfiche ↗

Questions and answers

How does a service integration sign in to Laserfiche Cloud?
Through a Service App. You create a service principal in Account Administration, register the app in the Developer Console, and generate an Access Key. The app signs a JWT with that key and posts it to signin.laserfiche.com/oauth/token with grant_type=client_credentials. The token carries scopes such as repository.Read and repository.Write.
What happens if a field update leaves a field out?
It is cleared. A PUT to Entries/{entryId}/Fields replaces the entry's field values, so the request must include every existing value you want to keep. Date values must not carry a time zone offset, or the request is rejected.
Does the Repository API return search results at once?
No. SearchAsync answers 202 Accepted with a taskId. You poll Tasks?taskIds= until the status is Completed, then read Searches/{taskId}/Results, with ContextHits for each row. Cancelling a running task can leave partial results.
Ask about Laserfiche

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Laserfiche through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy