---
title: "Admit From Waitlist"
method: POST
path: "/api/v1/internal/self-serve/waitlist/admit"
tags: ["internal", "self-serve"]
---

# Admit From Waitlist

`POST /api/v1/internal/self-serve/waitlist/admit`

Admit a named waiting person, consuming a seat from the same cap.

Not gated by the admissions pause — an operator hand-picking someone is the
exception that control exists to allow — but the cap still binds, so a full
cohort refuses.

## Request body

- AdmitAccountRequest
  - `email` string, email, required

## Response `200`

Successful Response

- AdmitAccountResponse
  - `account_id` string, uuid, required
  - `state` 'pending' | 'waitlisted' | 'preparing' | 'ready' | 'failed', required — Where a self-serve account sits between signup and a usable workspace. ``PREPARING`` and ``READY`` hold a seat against the admission cap; the other three do not. Setup consumes capacity from the moment it starts rather than when it finishes, so a burst of in-flight setups cannot collectively pass the cap. See ``SEAT_HOLDING_STATES``.
  - `workflow_id` string, nullable, required

## Other responses

- `422` — Validation Error

## Changes

- **2026-08-25** `b61a1454aad6` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/maia-analytics/apis/maia-api/changes/api/v1/internal/self-serve/waitlist/admit/post.md)

---

[API](https://skmtc.dev/maia-analytics/apis/maia-api.md) · [All operations](https://skmtc.dev/maia-analytics/apis/maia-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/maia-analytics/maia-api/revisions/4c1b045ef2af/schema)