You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Documentation for endpoints in the "Custom Fields" page's "The custom field options object" section contain example requests that describe the need for an HTTP On-Behalf-Of header, when submitting an HTTP request. For example:
FWIW I didn't do an exhaustive audit of the other sections on the "Custom Fields" page. However, the first few that I spot checked -- "Activity Feed", "Applications", "Approvals", "Candidates" -- looked fine.
The text was updated successfully, but these errors were encountered:
Documentation for endpoints in the "Custom Fields" page's "The custom field options object" section contain example requests that describe the need for an HTTP
On-Behalf-Of
header, when submitting an HTTP request. For example:Several endpoints already include a "Headers" section, which provides a description of the
On-Behalf-Of
header like so:However, other endpoints in that same section do NOT contain a "Headers" section:
The list of endpoints in the "The custom field options object" section that are missing a "Headers" section:
FWIW I didn't do an exhaustive audit of the other sections on the "Custom Fields" page. However, the first few that I spot checked -- "Activity Feed", "Applications", "Approvals", "Candidates" -- looked fine.
The text was updated successfully, but these errors were encountered: