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

# Import agent builder conversations kept in a browser

> Move the threads a browser kept for one saved agent onto your account, once. Send them as the browser holds them, without the two prompt texts of each diff: only what was asked, what changed and the line counts are kept. The newest ten are kept, each with its last forty turns; more is trimmed rather than refused, and a thread with nothing asked is skipped. A thread already imported under the same `local_id` is skipped too, so a retried import creates nothing twice; `already_present` says how many were.



## OpenAPI

````yaml /openapi.json post /agents/assistant/conversations/import/
openapi: 3.1.0
info:
  contact:
    email: support@getoneprofile.ai
    name: Oneprofile Support
  description: >-
    REST API reference for Oneprofile, the GTM data layer for your CRM. Manage
    tables, enrichments, and integrations. Authenticate with an API key to get
    started.
  termsOfService: https://www.getoneprofile.ai/terms
  title: API Reference | Oneprofile
  version: '0.0'
servers:
  - url: https://api.getoneprofile.ai
security: []
tags:
  - description: >-
      The docked AI Assistant: its general chat about the workspace and the
      product, streamed as Server-Sent Events, and the one list of a person's
      threads across every assistant, with pin, rename, delete and the
      search-to-table link.
    name: assistant
  - description: >-
      Granted workspace actions: what the AI Assistant proposed or applied in a
      conversation, the approve, dismiss and undo decisions on each card, the
      workspace's approval threshold and default grants, and the eight verbs.
    name: workspace-actions
  - description: >-
      The agent builder's saved conversations: threads of prompt edits, the
      turns recorded on them, and the one-time import from the browser.
    name: agent-assistant
  - description: >-
      The Getting started checklist: a workspace's progress through the six
      steps from its first people search to its first launched sequence.
    name: onboarding
  - description: Sender profiles, connected mailboxes, tags, and the Google connect flow.
    name: senders
  - description: The workspace do-not-contact list, enforced before every send.
    name: suppression
  - description: >-
      The workspace's recontact rule: how long before anyone hears from us
      again.
    name: contact_cooldown
  - description: 'Sequence authoring: the graph, the table-backed audience, previews.'
    name: sequences
  - description: >-
      The LinkedIn channel: connecting an account to a sender, its safety limits
      and history, and the protocol the browser extension speaks.
    name: linkedin
  - description: >-
      The approval queue: everything waiting on a person across every sender and
      channel, and the workspace's manual or automatic modes per channel.
    name: outreach
  - description: 'The unified outreach inbox: threads, replies, labels, events.'
    name: inbox
  - description: 'The AI reply layer: workspace settings, drafts, and approval.'
    name: inbox-ai
  - description: Notification rules, per-user preferences, and the Slack connection.
    name: notifications
  - description: Endpoints for seeing all available integration types.
    name: integration-types
  - description: Endpoints for creating and managing integrations.
    name: integrations
  - description: Endpoints for the generic OAuth install/claim app-listings engine.
    name: app-listings
  - description: Endpoints for creating and managing API keys.
    name: apikey
  - description: Endpoints for managing billing and subscription information.
    name: billing
  - description: Endpoints for creating and managing tables.
    name: tables
  - description: Endpoints for table columns, formula previews, and on-demand column runs.
    name: table-columns
  - description: Endpoints for table rows and manual cell edits.
    name: table-rows
  - description: Endpoints for observing and cancelling table recompute runs.
    name: table-runs
  - description: >-
      Endpoints for org-shared per-column display preferences: hidden, pinned,
      width, and colour tint.
    name: table-ui-prefs
  - description: >-
      Endpoints for the org-shared names given to the column tint palette: what
      this organisation calls each colour. Org-level, not per-table.
    name: table-column-color-labels
  - description: >-
      Endpoints for the enrichment action catalog, model list, presets, draft
      generation, and saved agents.
    name: table-enrichments
  - description: >-
      Endpoints for teaching a saved agent from example rows: training sessions,
      per-row feedback, and the proposed prompt to approve.
    name: agent-training
  - description: >-
      The durable audit trail of a table's enrichment actions: configured,
      edited, run, cancelled, and settled cost.
    name: table-enrichment-audit-logs
  - description: Endpoints for saving and applying column templates.
    name: table-templates
  - description: Server-sent change feed for a table's grid.
    name: table-events
  - description: 'Endpoints for org-shared saved table views: sort, filters, hidden columns.'
    name: table-views
  - description: >-
      The per-table AI Assistant: named conversations, the column suggestions a
      build turn produces, and the questions an analyze turn answers.
    name: table-assistant
  - description: >-
      Endpoints for PER-USER table preferences: favourites and recently opened.
      Unlike the rest of the table surface these are personal, so two members of
      one organisation legitimately see different answers.
    name: table-user-prefs
  - description: >-
      Endpoints for building a table from an uploaded CSV: upload and preview
      the inferred columns, commit the reviewed mapping, then poll the row load.
    name: table-imports
  - description: Endpoint for downloading a table's rows as CSV.
    name: table-export
  - description: >-
      Endpoints for the integration a table imports from: attach and preview it,
      promote imported fields into columns, and run the import on demand.
    name: table-sources
  - description: >-
      Endpoints for a table's recurring import cadence: set it, pause it, and
      read the next fire times.
    name: table-schedules
  - description: >-
      Endpoints for pushing a table's rows out to a connected integration: list
      writable destinations, derive their write capabilities, and map export
      columns.
    name: table-writeback
  - description: >-
      Endpoints backing a lookup column's setup: the connections whose records a
      column could read, and the identity fields one record type can be looked
      up by.
    name: table-integration-lookup
  - description: >-
      Endpoints for sourcing leads from the lead database: count and preview
      matches, land them in a table, and keep saved searches. Alongside people
      and company searches, leads can be sourced from buying signals — what a
      company or person just did — with a catalogue endpoint behind the picker
      that builds them.
    name: find-leads
  - description: >-
      Endpoints for discovering a domain's subdomains from public certificate
      logs and landing the results in a table.
    name: find-subdomains
  - description: Endpoints for the credit balance meter and usage reporting.
    name: credits
  - description: >-
      Endpoints for the workspace referral program: the shareable link, the
      friends who joined through it, and claiming a code after signup.
    name: referral
  - description: >-
      Endpoints for the affiliate program's own dashboard: enrolling and
      claiming a code, the summary, stats and activity feed, the commission
      ledger, and identity verification and payouts.
    name: affiliate
  - description: >-
      Endpoints for the design partner program's customer surface: whether this
      workspace is a design partner, the badges its feedback has earned, and
      sending and reading that feedback.
    name: design-partner
  - description: >-
      Endpoints for the org-level AI business context — company description,
      ideal customer profile, buyer personas, interest signals and social proof
      — plus domain-based generation and the reference documents whose summaries
      ride alongside those fields.
    name: ai-context
  - description: >-
      Endpoints for the signed-in user's Google Drive connection: starting and
      finishing the OAuth grant, checking or dropping it, and minting the
      short-lived token the Google Picker needs.
    name: google-drive
paths:
  /agents/assistant/conversations/import/:
    post:
      tags:
        - agent-assistant
      summary: Import agent builder conversations kept in a browser
      description: >-
        Move the threads a browser kept for one saved agent onto your account,
        once. Send them as the browser holds them, without the two prompt texts
        of each diff: only what was asked, what changed and the line counts are
        kept. The newest ten are kept, each with its last forty turns; more is
        trimmed rather than refused, and a thread with nothing asked is skipped.
        A thread already imported under the same `local_id` is skipped too, so a
        retried import creates nothing twice; `already_present` says how many
        were.
      operationId: import_agent_chat_conversations
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/AgentChatImportSchema'
        required: true
      responses:
        '201':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AgentChatImportResponseSchema'
          description: Successful Response
        '401':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UnauthorizedResponse'
          description: Unauthorized
        '403':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ForbiddenResponse'
          description: Forbidden
        '422':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UnprocessableEntityResponse'
          description: Invalid request made to the API.
        '500':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServerErrorResponse'
          description: Internal server error.
        '502':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServerErrorResponse'
          description: Bad gateway error.
        '503':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServerErrorResponse'
          description: Service unavailable.
      security:
        - APIKeyHeader: []
        - HTTPBearer: []
components:
  schemas:
    AgentChatImportSchema:
      description: >-
        The threads a browser kept for one agent, newest first, to move onto the
        account.
      properties:
        saved_agent_id:
          description: The saved agent the threads are about.
          format: uuid
          title: Saved Agent Id
          type: string
        threads:
          items:
            $ref: '#/components/schemas/AgentChatImportThreadSchema'
          maxItems: 20
          title: Threads
          type: array
      required:
        - saved_agent_id
        - threads
      title: AgentChatImportSchema
      type: object
    AgentChatImportResponseSchema:
      description: What one import did.
      properties:
        already_present:
          description: Threads skipped because you had imported them before.
          title: Already Present
          type: integer
        conversations:
          description: The threads this request created, in the order given.
          items:
            $ref: '#/components/schemas/AgentChatConversationReadSchema'
          title: Conversations
          type: array
        total_count:
          title: Total Count
          type: integer
      required:
        - conversations
        - total_count
        - already_present
      title: AgentChatImportResponseSchema
      type: object
    UnauthorizedResponse:
      properties:
        detail:
          description: The detail of why the request is unauthorized.
          title: Detail
          type: string
      required:
        - detail
      title: UnauthorizedResponse
      type: object
    ForbiddenResponse:
      properties:
        detail:
          description: The detail of why the request is forbidden.
          title: Detail
          type: string
      required:
        - detail
      title: ForbiddenResponse
      type: object
    UnprocessableEntityResponse:
      properties:
        detail:
          description: >-
            The detail of the error. This is the error message to show to the
            user. You should also use the issues field to show more detailed
            error messages per field. Use this field for a single liner error
            message.
          title: Detail
          type: string
        issues:
          description: >-
            The issues that caused the error. There can be multiple issues. Each
            issue is a user-facing error message.
          items:
            $ref: '#/components/schemas/UnprocessableEntityIssue'
          title: Issues
          type: array
      required:
        - detail
        - issues
      title: UnprocessableEntityResponse
      type: object
    ServerErrorResponse:
      properties:
        detail:
          description: The detail of why the server returned an error.
          title: Detail
          type: string
      required:
        - detail
      title: ServerErrorResponse
      type: object
    AgentChatImportThreadSchema:
      description: One thread a browser kept, in the shape the browser holds it.
      properties:
        local_id:
          anyOf:
            - maxLength: 64
              minLength: 1
              type: string
            - type: 'null'
          description: >-
            The browser's own id for the thread. A thread you already imported
            under this id is skipped, so sending the same one twice imports it
            once.
          title: Local Id
        started_at:
          anyOf:
            - format: date-time
              type: string
            - type: 'null'
          title: Started At
        task:
          default: ''
          description: The build task that opened the thread, when it came from a build.
          maxLength: 4000
          title: Task
          type: string
        turns:
          items:
            $ref: '#/components/schemas/AgentChatImportTurnSchema'
          maxItems: 200
          title: Turns
          type: array
      required:
        - turns
      title: AgentChatImportThreadSchema
      type: object
    AgentChatConversationReadSchema:
      description: One thread, as Previous conversations lists it.
      properties:
        created_at:
          format: date-time
          title: Created At
          type: string
        id:
          format: uuid
          title: Id
          type: string
        last_message_at:
          anyOf:
            - format: date-time
              type: string
            - type: 'null'
          title: Last Message At
        saved_agent_id:
          format: uuid
          title: Saved Agent Id
          type: string
        task_description:
          description: >-
            The build task that opened the thread; empty when it began from a
            saved agent.
          title: Task Description
          type: string
        title:
          title: Title
          type: string
      required:
        - id
        - saved_agent_id
        - title
        - task_description
        - last_message_at
        - created_at
      title: AgentChatConversationReadSchema
      type: object
    UnprocessableEntityIssue:
      properties:
        input:
          anyOf:
            - type: string
            - type: integer
            - type: number
            - type: boolean
            - items: {}
              type: array
            - additionalProperties: true
              type: object
          description: The user's input that caused the error.
          title: Input
        loc:
          description: >-
            The location of the error. Always contains 1 or 2 elements. The
            first element is the type of location (e.g. 'body', 'query', 'path',
            'header'). The second element is the name of the field that caused
            the error. If the error is not related to a specific field, the
            second element is not present.
          items:
            type: string
          title: Loc
          type: array
        msg:
          description: The message of the error. The error message to show to the user.
          title: Msg
          type: string
        type:
          description: >-
            The type of the error. Useful for frontend code to handle different
            types of errors.
          title: Type
          type: string
      required:
        - loc
        - msg
        - type
        - input
      title: UnprocessableEntityIssue
      type: object
    AgentChatImportTurnSchema:
      description: One turn of a thread a browser kept, in the shape the browser holds it.
      properties:
        diff:
          anyOf:
            - $ref: '#/components/schemas/AgentChatImportDiffSchema'
            - type: 'null'
        failed:
          default: false
          title: Failed
          type: boolean
        request:
          maxLength: 4000
          title: Request
          type: string
        summary:
          anyOf:
            - maxLength: 2000
              type: string
            - type: 'null'
          title: Summary
      required:
        - request
      title: AgentChatImportTurnSchema
      type: object
    AgentChatImportDiffSchema:
      description: >-
        The diff a browser kept for one turn. Only its counts move; the two
        texts are not kept.
      properties:
        counts:
          $ref: '#/components/schemas/AgentChatImportCountsSchema'
      required:
        - counts
      title: AgentChatImportDiffSchema
      type: object
    AgentChatImportCountsSchema:
      description: The diff counts a browser kept for one turn.
      properties:
        added:
          default: 0
          maximum: 100000
          minimum: 0
          title: Added
          type: integer
        removed:
          default: 0
          maximum: 100000
          minimum: 0
          title: Removed
          type: integer
      title: AgentChatImportCountsSchema
      type: object
  securitySchemes:
    APIKeyHeader:
      in: header
      name: X-API-Key
      type: apiKey
    HTTPBearer:
      scheme: bearer
      type: http

````