Create ICP

Create a new Ideal Customer Profile (ICP).

An ICP defines the target company and people segments for signal discovery.

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:

• name: A descriptive name for the ICP (e.g., “Mid-market SaaS companies in US”).
• target_roles: List of job titles or role descriptions to target. Examples: [“Head of Engineering”, “VP of Product”, “Senior Leaders in Engineering & Product”].
• employee_ranges: Company size filters. Provide one or more range labels from the employee_ranges list returned by /api/v1/icp/options. Multiple ranges are collapsed to an overall min/max employee count internally.
• location: List of company HQ location codes. Use the value field from the locations list returned by /api/v1/icp/options (e.g., [“us”, “uk”, “ca”]).

Optional fields:

• min_funding / max_funding: Funding stage range. Both must be provided together. Use values from the funding_stages list returned by /api/v1/icp/options.
• employee_count_funding_config: How to combine employee count and funding criteria. Only valid when funding is set. Values: "AND" (company must match both employee count AND funding stage) or "OR" (company must match either). Omit or set to null if no combination logic is needed.
• sub_locations: US state or city codes. Use the value field from the sub_locations list returned by /api/v1/icp/options (e.g., [“ca”, “san-francisco-ca”, “ny”]). Only applicable when location is exclusively ["us"].
• people_locations: Geographic filter for target people. Use the value field from the people_locations list returned by /api/v1/icp/options (e.g., [“us”, “ca”]).
• people_sub_locations: Sub-region codes for people locations. Use the value field from the people_sub_locations list returned by /api/v1/icp/options (e.g., [“san-francisco-ca”, “austin-tx”]). Only applicable when people_locations is exclusively ["us"].

POST /api/v1/icp/create

Create ICP

cURL

curl --request POST \
  --url https://api.openfunnel.dev/api/v1/icp/create \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <x-api-key>' \
  --header 'X-User-ID: <x-user-id>' \
  --data '
{
  "name": "<string>",
  "target_roles": [
    "<string>"
  ],
  "employee_ranges": [
    "<string>"
  ],
  "location": [
    "<string>"
  ],
  "min_funding": "<string>",
  "max_funding": "<string>",
  "sub_locations": [
    "<string>"
  ],
  "people_locations": [
    "<string>"
  ],
  "people_sub_locations": [
    "<string>"
  ]
}
'

200

{
  "icp": {
    "id": 123,
    "name": "<string>",
    "target_roles": [
      "<string>"
    ],
    "min_employee": 123,
    "max_employee": 123,
    "min_funding": "<string>",
    "max_funding": "<string>",
    "location": [
      "<string>"
    ],
    "sub_locations": [
      "<string>"
    ],
    "people_locations": [
      "<string>"
    ],
    "people_sub_locations": [
      "<string>"
    ],
    "employee_count_funding_config": "<string>"
  }
}

Headers

X-API-Key · string · required

X-User-ID · string · required

Body

application/json

name · string · required

target_roles · string[] · required

employee_ranges · string[] · required

location · string[] · required

min_funding · string | null

max_funding · string | null

employee_count_funding_config · enum<string> | null

Available options: AND, OR

sub_locations · string[] | null

people_locations · string[] | null

people_sub_locations · string[] | null

Response

200

application/json

Successful Response

icp · ICPItem · object · required

Show child attributes