POST
/portfolios/{portfolio_gid}/removeCustomFieldSettingRemove a custom field from a portfolio
Removes a custom field setting from a portfolio. Supply the custom field identifier in the data block to identify the setting to remove. A successful response contains an empty data object.
- RetriesRetries up to 2×, 500ms backoff, 30s timeout.
Custom field setting removal details wrapped in a data object. custom_field identifies the setting to remove.
dataobjectoptional
200Returns an empty `data` object after the custom field setting is successfully removed from the portfolio.
dataobjectoptional
An empty object. Some endpoints do not return an object on success. The success is conveyed through a 2-- status code and returning an empty object.
400Returned when `custom_field` is missing or the request is malformed.
errorsarray<object>optional
401Returned when the request does not include a valid authentication token.
errorsarray<object>optional
403Returned when the authenticated user does not have access to the portfolio or the required `portfolios:write` scope.
errorsarray<object>optional
404Returned when the portfolio or custom field setting does not exist, or the method and path do not identify a known action.
errorsarray<object>optional
500Returned when the API encounters a server-side failure.
errorsarray<object>optional
Error handling
A 400 is returned when custom_field is missing or the request is malformed. A 401 indicates that no valid authentication token was provided, while a 403 indicates that the authenticated user lacks access to the portfolio or the required portfolios:write scope. A 404 indicates that the portfolio or custom field setting does not exist, and a 500 indicates a server-side failure.