Replace the ideal client profile
Changes the user's ideal client profile (ICP), which decides who counts as a lead. Replaces the ideal client: the include rules (who fits) and the exclude rules (who never fits). The rules cover job titles, seniorities, industries, company sizes, countries and more. A rule left out becomes empty, so start from get_icp and send back every rule you want to keep. Ziplined scores everyone again in the background. The answer gives the saved profile as a sentence, and how many people are a lead under it. It also gives the run that rescores them: poll it with refresh_data and its run_id. Costs no credits.
Use when: After get_icp, when the user wants to change who counts as a lead.
Do not use for: Only changing who never fits (use save_exclusions instead). Marking one person not a fit (use update_person instead). Rescoring without a change (use refresh_data instead).
Example: {"include":{"seniorities":["C-Level","Founder"],"industries":["Software Development"],"countries":["NL"]},"exclude":{"job_titles":["recruiter"]}}
PUT
Replace the ideal client profile
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Headers
Any client-chosen key, a uuid for example. Sending the same request twice with the same key has one effect and returns the same response twice; the same key with a different body returns 409.
Required string length:
1 - 255Example:
"3f1b2c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d"
Body
application/json