> ## Documentation Index > Fetch the complete documentation index at: https://docs.ziplined.io/llms.txt > Use this file to discover all available pages before exploring further. # People who almost fit the ideal client > Finds the people who almost fit the ideal client: they match every part except one. They become leads when the ideal client gets a little wider. They hit no exclusion, Ziplined has read their profile, and nobody marked them not a fit. It shows them in up to three groups, such as "15 people match everything except country: Belgium". Each group says how many people it holds. It also says which values to add to the ideal client to make them leads. When the user asks to act on one group, start from get_icp. Add the add values to include, and save_icp with the whole profile. First tell the user how many people become leads. When has_sync is true, also tell them that their syncs send those people one time. Use when: The user asks who almost fits, or who misses on just one thing. Also who would count as a lead with a looser ideal client. Also why there are so few leads, or who they are missing. Do not use for: The leads themselves, or people found by filters (use search_people instead). Why one person is not a lead (use get_person instead, and its missed). ## OpenAPI ````yaml /openapi.json get /v1/icp/almost-leads openapi: 3.1.0 info: title: Ziplined API version: 1.0.0 description: >- LinkedIn engagement data about people, companies and posts. The workspace comes from the credential; lists page with `limit` and `cursor`. servers: - url: https://api.ziplined.io description: Production security: [] tags: - name: People description: The people in your workspace, and what you sent them. - name: Companies description: The companies those people work at. - name: Posts description: Your own posts and their numbers. - name: Engagements description: One act by one person on one post. - name: Insights description: Period against period, and the series behind it. - name: Views description: The saved views of the app, and who is in a hand-picked one. - name: Audiences description: The scored target groups, and their membership. - name: ICP description: 'Who you sell to: the rules every person is scored against.' - name: Sources description: What your radar collects from. - name: Account description: Who is asking, what is set up, and what is next. - name: Credits description: What is left to spend on sources, and when it resets. - name: Integrations description: 'Where syncs send people: webhook, email, Slack and app destinations.' paths: /v1/icp/almost-leads: get: tags: - ICP summary: People who almost fit the ideal client description: >- Finds the people who almost fit the ideal client: they match every part except one. They become leads when the ideal client gets a little wider. They hit no exclusion, Ziplined has read their profile, and nobody marked them not a fit. It shows them in up to three groups, such as "15 people match everything except country: Belgium". Each group says how many people it holds. It also says which values to add to the ideal client to make them leads. When the user asks to act on one group, start from get_icp. Add the add values to include, and save_icp with the whole profile. First tell the user how many people become leads. When has_sync is true, also tell them that their syncs send those people one time. Use when: The user asks who almost fits, or who misses on just one thing. Also who would count as a lead with a looser ideal client. Also why there are so few leads, or who they are missing. Do not use for: The leads themselves, or people found by filters (use search_people instead). Why one person is not a lead (use get_person instead, and its missed). responses: '200': description: The result content: application/json: schema: type: object properties: almost_leads: type: object properties: total: type: integer description: >- Everyone who misses exactly one part of the ideal client, also outside the groups below. groups: type: array items: type: object properties: part: type: string enum: - roles - companySize - industry - country description: >- The one part of the ideal client sentence these people miss. part_label: type: string description: That part in words, for example country. value: type: string description: >- Their value for that part, as stored, for example BE. label: type: string description: That value in words, for example Belgium. people: type: integer description: >- How many people are in this group. Groups never share a person. become_leads: type: integer description: >- How many people the change makes leads. Larger than people only when a size change fills a gap of several bands. action: type: string description: The change in words, for example Add Belgium. summary: type: string add: type: object properties: job_titles: type: array items: type: string seniorities: type: array items: type: string industries: type: array items: type: string company_sizes: type: array items: type: object properties: min: type: integer max: type: integer required: - min - max countries: type: array items: type: string description: >- The values to add to include to make this group leads. Add them to the lists get_icp returns and send the whole profile with save_icp. required: - part - part_label - value - label - people - become_leads - action - summary - add maxItems: 3 description: >- The three largest groups, largest first. Empty when nobody almost fits. has_sync: type: boolean description: >- True when a view syncs somewhere. Then its syncs send the new leads one time. required: - total - groups - has_sync required: - almost_leads '400': description: A filter value is invalid, or this resource has no such filter. content: application/json: schema: $ref: '#/components/schemas/Error' '401': description: Missing or invalid bearer token. content: application/json: schema: $ref: '#/components/schemas/Error' '403': description: Wrong workspace, or the credential lacks the required scope. content: application/json: schema: $ref: '#/components/schemas/Error' security: - bearerAuth: [] components: schemas: Error: type: object properties: error: type: object properties: code: type: string message: type: string required: - code - message required: - error securitySchemes: bearerAuth: type: http scheme: bearer ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.