---
title: "Advance the authenticated onboarding flow from setup to books"
method: POST
path: "/onboarding/v3/books/open"
tags: ["Onboarding"]
---

# Advance the authenticated onboarding flow from setup to books

`POST /onboarding/v3/books/open`

## Request

- Base URL: `https://api.medianfi.com/api/v1`
- URL: `https://api.medianfi.com/api/v1/onboarding/v3/books/open`
- Auth: HTTP bearer

The empty request cannot choose a company or lifecycle stage. The server resolves the flow-owned QA company and performs an idempotent setup-to-books transition.

## Headers

- `X-Median-App-Surface` 'qa'

## Request body

- OnboardingV3EmptyBody

## Response `200`

Authoritative books stage

- OnboardingV3BooksOpenApiResponse
  - `success` true, required
  - `data` OnboardingV3BooksOpen, required
    - `companyId` string, uuid, required
    - `stage` 'books', required
    - `opened` boolean, required

## Other responses

- `400`: Onboarding request body is not valid JSON
- `401`: Authentication required
- `403`: Insufficient permissions or not a company member
- `404`: Resource not found
- `409`: Request conflicts with the durable onboarding state
- `413`: Onboarding setup request exceeds the 32768-byte route limit
- `415`: Onboarding request charset or content encoding is unsupported
- `422`: Validation error

---

[API](https://skmtc.dev/medianfi/apis/median-api.md) · [All operations](https://skmtc.dev/medianfi/apis/median-api/llms.txt) · [OpenAPI document](https://skmtc.dev/medianfi/apis/median-api/revisions/20090ea32b0d?raw)