I am writing to submit a detailed feature request for a critical gap in the current Freshservice API: the inability to programmatically access the configurations for "Business Rules for Forms".
1. Problem Statement
The client-side logic that governs dynamic form behavior—such as conditionally showing, hiding, or mandating fields—is a powerful feature. However, these rules are only configurable through the UI. The existing /api/v2/business_rules endpoint is unrelated, as it pertains to server-side automations, not the client-side form logic we need to access.
This lack of API access creates significant operational challenges for maintaining governance, compliance, and documentation at scale.
2. Key Use Cases and Business Justification
An API endpoint for form rules would enable the following critical capabilities:
-
Governance and Compliance Audits: We need to perform regular audits to ensure our service request forms adhere to specific compliance standards. A manual review of dozens or hundreds of rules across multiple workspaces is inefficient and prone to human error. An API would allow us to build automated audit scripts.
-
Automated Documentation: Manually documenting complex, nested conditional logic for our forms is a significant administrative burden. An API would allow us to generate living documentation, ensuring our knowledge base is always in sync with the live configuration.
-
Impact and Dependency Analysis: Before modifying a form field, we need to understand which rules depend on it. Without an API, this requires a manual, painstaking search through the UI. An API would allow us to run a query to instantly find all dependencies.
-
Configuration Management (DevOps/Config-as-Code): For mature IT organizations, managing configuration as code is a best practice. An API would be the first step toward allowing us to store form rule definitions in a version control system (like Git), track changes, and potentially deploy them across environments (e.g., from Sandbox to Production).
3. Proposed Technical Solution
We propose the creation of a new, dedicated REST API endpoint. A read-only (GET) implementation would already provide immense value.
Suggested Endpoint:
GET /api/v2/form_rules (to list all rules)
GET /api/v2/form_rules/[id] (to retrieve a specific rule)
Conclusion
Exposing "Business Rules for Forms" via the API is no longer a "nice-to-have" but a fundamental requirement for enterprise-level management and governance. We strongly believe this feature would be highly valued by many of your customers who rely on Freshservice to manage complex service delivery processes.
We would appreciate it if you could forward this request to the product development team for their consideration in an upcoming release cycle.
Thank you for your time and dedication to improving the Freshservice platform.
