I know this topic has come up in various Answers posts, but I haven’t found a centralized or official feature request, so I’m submitting one here: Laserfiche needs an officially documented Forms API.

Having a supported, stable API for Forms would unlock a wide range of capabilities for both self-hosted and cloud customers. Here are a few high‑impact examples:

1. Migration Path to LF Cloud: Laserfiche has been emphasizing cloud adoption with new migration utilities, classes, and incentives, even the questions on the Empower 2026 Registration form. However, once in LF Cloud, customers lose direct access to the Forms database. Many of us rely heavily on database queries for business-critical processes—for example:
   - Sending daily reminders based on task activity per process
   - Checking whether an instance with a particular variable value already exists
   An official API would provide a supported replacement for this functionality.
2. Ability to Programmatically Cancel Instances: Workflow or third‑party systems often need to make decisions based on external logic. The ability to cancel a Forms instance through an API call would enable automated cleanup, error handling, and integration scenarios that are currently impossible without unsupported methods.
3. Ability to Update Instances and Reassign User Tasks: Organizations with high task volume or turnover frequently need to:
   - Update instance variables
   - Reassign user tasks programmatically
   These capabilities have been requested several times and would significantly improve automation and reduce manual admin work.
4. More Reliable Integrations: Right now, anyone who reverse‑engineers internal endpoints risks breaking changes with each release. A documented API would:
   - Enable stable, long‑term integrations
   - Build confidence for partners and developers investing in the platform

These are just a few examples; there are many more scenarios that would benefit from an officially supported Forms API. I’m sure others in the community will have additional use cases to add.