We are excited to announce the version 2 release of the Repository Cloud API which brings new capabilities such as PDF page generation on import, robust document export options (Image, Text, and Electronic Document), large file upload support up to 64GB, standardized long operation APIs, and many developer ergonomics improvements. A corresponding JavaScript API client library has also been released to make it easier for JavaScript developers to integrate with the Laserfiche repository with .NET and Java versions coming soon. To find out more, or experiment with the new version in Swagger, visit developer.laserfiche.com.
Announcement
Announcement
Announcing Repository Cloud API Version 2
Replies
The page generation on import is a very welcome feature because it means we can use capture profiles to run on docs that import through the API. Thanks for the major advance in capability here Andrew.
When can we expect V2 of self-hosted similar to cloud?
I don't have a target date at this time but we understand the need for the capabilities in v2 for our self-hosted customers. I hope to have an update in the near future.
Do we have an update on the v2 release for LF11 Self-Hosted? I have not heard or seen anything since Empower.
Thanks so much!
We haven't forgotten about this and are trying hard to get this released, but we haven't finalized a date yet. Hopefully I'll have an update soon with more information on a release timeframe.
Andrew
Hi Andrew, can you give us an update? We have a specific need with a client. Thanks!
According to the Laserfiche 12 Release Timeline look for it in Spring 2025.
Thanks!
We're also looking forward to this release, I'll check back next month.
Hi,
Any update on a timeline for V2 for self hosted?
I'll add my name to the list of people eagerly awaiting V2 for self hosted
Hi David,
I realize it's been a bit since we last posted an update. The current estimate is around the end of the year 2025, maybe a bit into the start of 2026. On the plus side, that estimate has more quantitative justification then some of the past ones, although we didn't quite realize it at the time. Basically, turns out there were some related updates that needed to happen as precursors that weren't neccessarily factored in, now they are.