Private Connected Field Options Require Private Field Access
5 days ago
- Form questions connected to a private custom field no longer return that custom field's current options unless the API key is allowed to access private fields. This affects
jobPosting.info,feedbackFormDefinition.list,feedbackFormDefinition.info,surveyFormDefinition.list,surveyFormDefinition.infoandinterviewBriefing.info. Previously these endpoints returned the connected field's options regardless of the key's private-field access. - A key without private-field access receives the question's own configured options instead. For most forms that is a snapshot captured when the question was connected, so it may be stale rather than empty — it can omit options added to the custom field since, and can include options that are no longer valid.
- Because of that, a key without private-field access can no longer reliably determine the valid values for such a question. Values submitted through
applicationFeedback.submitare still validated against the custom field's real options, so a value taken from the returned snapshot may be rejected. Grant the key private-field access if it needs to read or write these questions.

