POST
/portfolios/{portfolio_gid}/removeMembersRemove users from a portfolio
Removes specified users from a portfolio's membership. Supply the user identifiers in members and use opt_fields when you need additional portfolio properties in the response. A successful response returns the updated portfolio record.
- RetriesRetries up to 2×, 500ms backoff, 30s timeout.
opt_fieldsarray<string>optional
A comma-separated selection of portfolio properties to include in the response, such as `archived`, `color`, `created_at`, `custom_field_settings`, or nested properties such as `created_by.name`. Omit it to use the default response fields.
Portfolio membership details wrapped in a data object. members identifies the users to remove.
dataobjectoptional
200Returns the updated portfolio record, including any properties selected through `opt_fields`.
dataobjectoptional
400Returned when `members` 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.
errorsarray<object>optional
404Returned when the portfolio or a specified user 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 members 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. A 404 indicates that the portfolio or a specified user does not exist, and a 500 indicates a server-side failure.