Cut Over Suite Membership — POST /api/v1/admin/maintenance/suite-membership-cutover
Cut Over Suite Membership
Stop writing (and reading) the legacy suite-membership tables: turn suite_membership_legacy_writes OFF.
Endpoint: POST /api/v1/admin/maintenance/suite-membership-cutover
Authentication: Send a signed-in user’s access token in Authorization: Bearer <access token>, or an API key in X-API-Key: <API key>.
- A minimum role applies. The source code names it.
Parameters
Section titled “Parameters”| Name | In | Required | Type | Default | Description |
|---|---|---|---|---|---|
X-API-Key | header | no | string or null | API key, as an alternative to the access token (see Authentication). |
Request body
Section titled “Request body”No request body.
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
200 | Successful Response | SuiteParityCutoverResult (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
Errors this endpoint returns, read from its source code:
409
It can also return 401 if your credential is missing or expired, 403 if your credential does not allow this request, and 404 if the item does not exist or you cannot see it. Your role, your project membership and the key’s scope decide what a credential allows. See Errors and retries.
More details
Section titled “More details”- Group: Admin Maintenance
- Operation ID:
cut_over_suite_membership_api_v1_admin_maintenance_suite_membership_cutover_post - Source code:
backend/app/routers/admin_maintenance.py, line 607 - Specification: OpenAPI JSON