Search and list people (contacts, candidates, talent) in the CRM.
The query param is a Lucene query_string.

Unqualified terms match name, emails, phones, titles, current_title, current_company, companies, skillsets3 (skills), tag_names, location, city, state, country, zip, description3 (person intake/recruiter notes — users often say "intake notes"; the API field is description), person_event_notes, and schedule-item (meeting) fields: schedule_item_titles, schedule_item_descriptions (meeting calendar description, not person intake notes), schedule_item_locations, schedule_item_outline_texts, and schedule_item_transcript_texts.
Schedule items are meetings/calendar events; outline and transcript fields cover AI Notetaker summaries and full transcriptions (users may say "notetaker" / "transcription notes").
Field-qualified terms (field:value), ranges, and boolean AND/OR/NOT also work over those fields plus id, created_at, updated_at, schedule_item_ids, schedule_item_start_times (use emails, not email), and current_experience_average_start_date — when the person's current title/role began, i.e. how long since their last promotion or title change. There is no direct "tenure at current company" field: for someone promoted internally, current_experience_average_start_date reflects only their current title's start, not when they joined that employer.
E.g. description3:"great guy", title:engineer AND location:austin, skillsets3:python AND current_company:"acme corp", emails:"[email protected]" OR phones:"+15555550100", updated_at:[now-12M TO now], schedule_item_titles:standup AND schedule_item_start_times:[now-30d TO now], schedule_item_transcript_texts:"comp package", schedule_item_outline_texts:next AND schedule_item_locations:zoom, current_experience_average_start_date:[* TO now-2y] (no title change in the last 2 years).
For intake-note searches, prefer description3: — do not look for an activity type named "intake".

Structured filters (separate params):

• person_type_id
• list_id
• person_global_status_id
• active_job_stage_id
• active_workflow_stage_id

Sort by created_at/updated_at; scroll pagination.

To resolve one or more already-known person IDs to their names/records (not a text search), do not query on id/person_id — use include_ids, or call people_show for a single ID.