---
title: "Resume setup with its private setup token"
method: GET
path: "/onboarding/{id}/status"
tags: ["public"]
---

# Resume setup with its private setup token

`GET /onboarding/{id}/status`

## Request

- Base URL: `https://api.mailly.site` (the document declares no server; this is the origin it was published from)
- URL: `https://api.mailly.site/onboarding/{id}/status`
- Auth: none required

Authorization: Bearer <setup_token> only permits checking this setup. 202 before human confirmation; 200 ready returns the mailbox address and the account API key the human approved handing to the agent. Store the key in secure credential storage and never show it in chat or logs. Ready status can be retried for 10 minutes after confirmation.

## Path parameters

- `id` string, uuid, required

## Response `200`

Ready (with the API key) or denied

- object
  - `success` boolean, required
  - `status` 'ready' | 'denied', required
  - `address` object
    - `id` string, required
    - `address` string, required
  - `api_key` string
  - `hint` string

## Other responses

- `202`: Waiting for human approval
- `400`: Invalid request
- `401`: Authentication required
- `403`: Not allowed
- `409`: Address unavailable or request already handled
- `410`: Request expired
- `429`: Too many requests
- `503`: Temporarily unavailable

---

[API](https://skmtc.dev/mailly/apis/mailly-api.md) · [All operations](https://skmtc.dev/mailly/apis/mailly-api/llms.txt) · [OpenAPI document](https://skmtc.dev/mailly/apis/mailly-api/revisions/1ceb29637301?raw)