Take the organization out of read-only mode

POST /api/auth/organizations/{organizationId}/go-live

Take the organization out of read-only mode: the business accepts Manifold acting for it, and from here outbound work runs — pushes to its sales channels and its ledger, mail to its customers and suppliers, webhooks to its apps.

Nothing refused while it was read-only is sent late; each integration catches up from the state as it now stands. Going live is where the organization starts paying: an organization billed through an app (the one whose install brought it) goes live only on a plan approved with that app's billing provider — 409 PlanRequiredToGoLive names the app and its plan page (plansUrl) to approve it on, and 503 PlanCheckUnavailable says billing did not answer; either way nothing changed, and this is asked before the books are opened. Going live opens the books: it commands inventory-manager to complete the opening stocktake (inventory.stocktake-completed, after inventory.stocktake-started when none is open) — the counts entered on it, every pair nobody counted at what inventory holds, every stock SKU at the cost entered or its cost basis — so the general ledger, and every ledger app's history, begins at go-live. 409 OpeningStocktakeIncomplete names the stock SKUs with no cost, and 503 OpeningStocktakeUnavailable says inventory did not answer; either way nothing changed. 403 AdminRequired for anyone but an owner or admin, MembershipDeactivated for a caller whose own access has ended; 409 SandboxNeverLive for a sandbox, which never goes live. Going live is final: once decided, read-only is refused with 409 GoLiveIsFinal. Appends auth.org-went-live. Idempotent by state: an organization that is already live is acknowledged and appends nothing.

Access

Requires a signed-in session: An active owner or admin of the organization, by their BetterAuth session or their own tenant JWT, checked against its membership by the route

How scopes come from roles: Scopes and roles. Getting a token: Authentication and app tokens.

Retries

Idempotent by state: an organization that is already live is acknowledged and appends nothing.

Why every write carries a key: Idempotency and retries.

Facts appended

auth.org-went-live

What a fact is: Facts and the journal.

AI agent tool

No agent tool. Going live is the business accepting that Manifold now writes to its store, its ledger and its customers: an owner's or admin's decision in Settings › General, never an agent's.

Connecting an agent: AI agents.

Example

curl

curl -X POST 'https://auth.getmanifold.io/api/auth/organizations/org_01a156d2-8680-7738-ab2e-ff985e454887/go-live' \
  -H "Authorization: Bearer $MANIFOLD_TOKEN"

JavaScript (fetch)

const response = await fetch("https://auth.getmanifold.io/api/auth/organizations/org_01a156d2-8680-7738-ab2e-ff985e454887/go-live", {
  method: "POST",
  headers: { Authorization: `Bearer ${process.env.MANIFOLD_TOKEN}` },
});
if (!response.ok) throw new Error(`${response.status}: ${await response.text()}`);
const answer = await response.json();

Response · 200 · application/json

{
  "organizationId": "org_01a156d2-8680-7738-ab2e-ff985e454887",
  "mode": "live",
  "changedAt": "2026-10-22T00:00:00.000Z",
  "changedBy": "usr_01a15709-7582-7646-b491-261a138f0650"
}

The panel writes this call in other languages. It does not send it: Manifold's APIs do not take calls from a web page on another site, so run the call from your own code or terminal. The whole API as OpenAPI: auth-service.openapi.json. Base URL https://auth.getmanifold.io.

Errors

Every refusal is a status and a JSON body whose _tag names it. A refused call changes nothing.

`401`

Refusal	What it means	What to do
`Unauthorized` reason	The token is missing, expired or not one Manifold issued.	Get a fresh token and send the call again.
`TokenAlreadyUsed` tokenId	A single-use app token was already spent.	Mint a new token for this call.

`402`

Refusal	What it means	What to do
`SubscriptionRequired` status	The organization's subscription has lapsed, so writes are refused.	An owner settles billing. Reads still work meanwhile.

`403`

Refusal	What it means	What to do
`AdminRequired`	Only an owner or admin of the organization may do this.	Ask an owner or admin.
`MembershipDeactivated`	Your own access to this organization has ended.	Ask an owner or admin to reactivate you.
`TenantRequired` userId	The token names no organization.	Choose the organization, then get a new token.
`ScopeRequired` required	The token's roles do not grant the scope this call needs.	Ask an owner or admin for a role that grants it.

`409`

Refusal	What it means	What to do
`SandboxNeverLive`	A sandbox never goes live.	Go live in the organization the sandbox belongs to.
`PlanRequiredToGoLive` appId, plansUrl	The request was refused, and nothing changed.	Nothing changed. Read the record, then decide.
`OpeningStocktakeIncomplete` stocktakeId, missing, skus	Some stock SKUs have neither a cost on the opening stocktake nor a cost basis. `skus` names them.	Enter a cost for each, then go live.
`MirroredFromSource` source	This area is fed by your source system until the organization goes live.	Make the change in the source system, or go live first.

`503`

Refusal	What it means	What to do
`PlanCheckUnavailable` reason	A service this call needs did not answer, so nothing changed.	Send the same request again shortly.
`OpeningStocktakeUnavailable` reason	The opening stocktake could not be completed just now, so the organization did not go live.	Send the same request again shortly.
`RequestLogUnavailable` tokenId, reason	The service could not record the request, so it did nothing.	Send the same request again shortly.

How refusals work everywhere: Errors.

Used in

Run beside your old system, then go live, step 5: Try to go live before it is valued
Run beside your old system, then go live, step 8: Go live