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

# Approve onboarding section

> Mark an onboarding section as approved by the user. The legacy final approval step completes onboarding without starting legacy scans.

**CLI:**

```bash theme={null}
pixie onboarding approve-section create --section <section>
pixie onboarding approve-section create --section <section> --run-first-scan
```

## Overview

Mark an onboarding section as approved by the user. The legacy final approval step completes onboarding without starting legacy scans.

This page documents `post /api/onboarding/approve-section`. Use the request and response sections on this page for accepted parameters, payload fields, response fields, and authentication behavior.

## AI agent notes

* Confirm the operation matches the user's intent before calling it.
* For write operations, confirm the user intends to change state.
* Surface validation, permission, and not-found errors instead of retrying unchanged.


## OpenAPI

````yaml post /api/onboarding/approve-section
openapi: 3.0.3
info:
  title: Pixie API
  version: 1.0.0
  description: >-
    HTTP API for the Pixie GTM platform - Lead Finder search preparation,
    campaign-backed Outbound execution, Pixie Agent runs, sender management, and
    Unibox reply workflows. Designed for operation by both humans and autonomous
    AI agents. Agents should start at the [Agent
    Playbook](/guides/agent-playbook) which prescribes a workspace-context check
    (`GET /api/context`) and core user journeys with exact call ordering.
  contact:
    name: Pixie Support
    url: https://pixie.ai
servers:
  - url: https://app.pixie.ai
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Campaigns
    description: >-
      Campaign-backed Outbound execution. These endpoints manage draft,
      launching, active, paused, and completed Outbound runs with sequence
      nodes, contacts, and sender accounts.
  - name: Accounts
    description: Signed-in user account, settings, and workspace context endpoints.
  - name: Billing
    description: Billing customer portal and account billing endpoints.
  - name: Senders
    description: >-
      Connected sender accounts, email inboxes, sending domains, DNS
      verification, warmup, and sender capacity.
paths:
  /api/onboarding/approve-section:
    post:
      tags:
        - Accounts
      summary: Approve onboarding section
      description: >-
        Mark an onboarding section as approved by the user. Once all three
        context sections are approved, `completeOnboarding` finishes onboarding.
      operationId: approveOnboardingSection
      parameters: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                section:
                  type: string
                  enum:
                    - company
                    - market
                    - signals_context
                  description: >-
                    Which onboarding section the user is approving. Approving
                    all three unlocks `completeOnboarding`.
                runFirstScan:
                  default: true
                  description: >-
                    Deprecated legacy Signals flag. Accepted for backward
                    compatibility and ignored.
                  type: boolean
              required:
                - section
                - runFirstScan
              additionalProperties: false
              description: >-
                Mark a per-section onboarding draft as approved by the user.
                Idempotent: re-approving a section is a no-op.
      responses:
        '200':
          description: Section approved.
          content:
            application/json:
              schema:
                type: object
                properties:
                  section:
                    type: string
                    description: Echo of the approved section key.
                  approved:
                    type: boolean
                    description: >-
                      Always `true` on a 200. The section is approved (whether
                      it was approved by this call or already approved).
                  onboardingCompleted:
                    type: boolean
                    description: >-
                      Deprecated. Always `false` — call `completeOnboarding` to
                      finish onboarding after all sections are approved.
                  signalScanTriggered:
                    type: boolean
                    description: >-
                      Deprecated legacy Signals field. Always `false` because
                      old scans are no longer triggered from onboarding.
                required:
                  - section
                  - approved
                  - onboardingCompleted
                  - signalScanTriggered
                additionalProperties: false
                description: Result of approving an onboarding section.
        '400':
          description: Missing onboarding session.
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                required:
                  - error
                additionalProperties: false
        '401':
          description: Unauthorized.
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                required:
                  - error
                additionalProperties: false
        '409':
          description: >-
            Section not ready, or prior section not yet approved. Sequential
            order is company -> market -> signals_context.
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                required:
                  - error
                additionalProperties: false
        '500':
          description: Internal server error.
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                required:
                  - error
                additionalProperties: false
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: pk_live_...

````