> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enginy.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Import a list from AI Finder

> Use AI Finder to generate a new contact or company search, then import the results into a destination list. This is the right workflow when the user asks for a new prospecting list rather than existing records already stored in Enginy. Returns an actions ID that can be monitored via GET /v1/actions/{actionsId}/status and queried via the existing contacts/companies endpoints using the actionsId filter. This endpoint always runs a brand-new search from `text` and does not accept a `previewId` — if you already have one from POST /v1/ai-finder/previews (or its iterate endpoint), use POST /v1/ai-finder/previews/{previewId}/import instead so your refinements are preserved.

    > **Required scope:** `ACTIONS_WRITE`
    >
    > **Rate limit:** 10 requests per minute



## OpenAPI

````yaml https://openapi.enginy.ai/definitions.json post /v1/ai-finder/import
openapi: 3.1.0
info:
  title: Enginy API
  version: 1.0.0
  description: Public API for Enginy platform
servers:
  - url: https://openapi.enginy.ai
    description: Configured server
security: []
tags:
  - name: AI Variables
    description: >-
      Manage AI variables and discover the entity fields you can reference in
      prompts and entity requests.
  - name: Inbox
    description: >-
      Inbox endpoints for listing contact threads, reading thread messages,
      managing tags, and sending manual replies.
  - name: Workflows
    description: >-
      Build, validate, publish, run, and inspect advanced (graph) workflows,
      plus the block/condition catalog needed to author a workflow plan.
paths:
  /v1/ai-finder/import:
    post:
      tags:
        - Lists
      summary: Import a list from AI Finder
      description: >-
        Use AI Finder to generate a new contact or company search, then import
        the results into a destination list. This is the right workflow when the
        user asks for a new prospecting list rather than existing records
        already stored in Enginy. Returns an actions ID that can be monitored
        via GET /v1/actions/{actionsId}/status and queried via the existing
        contacts/companies endpoints using the actionsId filter. This endpoint
        always runs a brand-new search from `text` and does not accept a
        `previewId` — if you already have one from POST /v1/ai-finder/previews
        (or its iterate endpoint), use POST
        /v1/ai-finder/previews/{previewId}/import instead so your refinements
        are preserved.

            > **Required scope:** `ACTIONS_WRITE`
            >
            > **Rate limit:** 10 requests per minute
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                text:
                  type: string
                  minLength: 1
                  maxLength: 500
                  description: >-
                    Natural-language description of the people or companies you
                    want AI Finder to locate.
                type:
                  type: string
                  enum:
                    - contacts
                    - companies
                  description: >-
                    Entity type to search and import. This determines whether
                    listId refers to a contact list or a company list.
                maxCount:
                  type: integer
                  minimum: 100
                  maximum: 2500
                  description: >-
                    Maximum number of results to import. Must be between 100 and
                    2500, inclusive, in increments of 100.
                listId:
                  type: integer
                  exclusiveMinimum: 0
                  description: >-
                    Destination list ID. Must be a contact list for contacts or
                    a company list for companies.
              required:
                - text
                - type
                - maxCount
                - listId
            examples:
              contactsImport:
                summary: Import contacts from AI Finder
                value:
                  listId: 123
                  maxCount: 500
                  text: VP Finance at companies in California
                  type: contacts
      responses:
        '201':
          description: AI Finder import started
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: string
                    enum:
                      - success
                  message:
                    type: string
                  data:
                    type: object
                    properties:
                      actionsId:
                        type: number
                        description: >-
                          Unique identifier for the actions group created for
                          this import
                      createdAt:
                        type: string
                        format: date-time
                        description: Date and time when the actions group was created
                      type:
                        type: string
                        enum:
                          - CONTACTS
                          - COMPANIES
                        description: Entity type imported into the destination list
                      listId:
                        type: number
                        description: Destination list ID
                      workflowId:
                        type: string
                        description: >-
                          Workflow ID that can be used with the public AI search
                          status endpoint
                    required:
                      - actionsId
                      - createdAt
                      - type
                      - listId
                      - workflowId
                required:
                  - status
                  - message
                  - data
        '400':
          description: Bad request - validation error
        '404':
          description: Destination list not found
        '422':
          description: >-
            AI Finder could not build a valid search or returned a different
            entity type
      security:
        - apiKey: []
components:
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: x-api-key

````