Targetprocess API currently bypasses UI-configured required field enforcement, allowing records to be created with missing required fields unless a separate Validation Rule exists.

Today, Targetprocess only enforces most required fields in the UI layer. As a result, items created through the API can bypass these required field checks unless a separate Validation Rule has been created. This creates inconsistent behavior between users creating items in the UI and integrations, automations, MCP servers, AI agents, or custom applications creating items through the API.

This enhancement would benefit organizations that rely on APIs, integrations, AI assistants, automation platforms, and third-party tools to create or update data in Targetprocess. It would improve data quality, reduce administrative overhead, and ensure a consistent user experience regardless of how data enters the system.

The proposed solution is to provide server-side enforcement of required fields so that any field marked as required is validated consistently across both the UI and API. If a required field is missing, the API should return a validation error similar to existing Validation Rules. Alternatively, the API should expose a comprehensive metadata endpoint that identifies all required fields (including those configured through Quick Add or other UI-based configurations) so external systems can dynamically determine and enforce field requirements before submitting requests. This would eliminate the need to create and maintain individual Validation Rules solely to enforce required fields.