---
title: "Get Member Onboarding Status"
method: POST
path: "/api/organization/member-onboarding/status"
tags: ["organization"]
---

# Get Member Onboarding Status

`POST /api/organization/member-onboarding/status`

Whether this member still owes the Google setup dialog for the active org.

POST rather than GET because a first-time evaluation PERSISTS its verdict — the
rules run once per (user, org) and never again, so a member's own Confirm/Skip can
never be re-derived away. The client only calls this when no status is recorded in
its already-loaded `users.preferences`, so it costs at most one request per
(user, org).

## Response `200`

Successful Response

- object

## Changes

- **2026-09-03** `cd6453ae5786` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/every/apis/every-api/changes/api/organization/member-onboarding/status/post.md)

---

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