Update an existing Ideal Customer Profile (ICP).
Only the fields included in the request body will be modified — all other
fields remain unchanged. The id field is always required to identify
which ICP to update.
Before calling this endpoint, call GET /api/v1/icp/options to retrieve
all valid values for employee_ranges, funding stages, locations, and sub_locations.
Required fields:
/api/v1/icp/list
or /api/v1/icp/create).Updatable fields (all optional — include only what you want to change):
employee_ranges list returned by /api/v1/icp/options.
Must contain at least one range if provided.value field from
the locations list returned by /api/v1/icp/options (e.g., [“us”, “uk”]).
Must contain at least one location if provided.null to clear (stored as "Any"). A value of "Any"
means no constraint on that bound. Use values from the funding_stages list
returned by /api/v1/icp/options."AND" or "OR". Only valid when funding is set. Set to
null to clear.value field from the
sub_locations list returned by /api/v1/icp/options
(e.g., [“ca”, “san-francisco-ca”]). Only applicable when location is
exclusively ["us"]. Set to null or [] to clear. If changing location
away from ["us"], you must also clear this field.value
field from the people_locations list returned by /api/v1/icp/options.
Set to null or [] to clear.value field from the people_sub_locations list returned by
/api/v1/icp/options. Only applicable when people_locations is
exclusively ["us"]. Set to null or [] to clear. If changing
people_locations away from ["us"], you must also clear this field.Cross-field validation:
sub_locations requires location to be ["us"] (checked against the
final merged state, not just the request).people_sub_locations requires people_locations to be ["us"].employee_count_funding_config requires at least one of min_funding or
max_funding to be a non-"Any" value.AND, OR Successful Response