Auth API · gridLayouts

How the signed-in person arranged the admin's lists

GET /api/auth/me/grid-layouts

How the signed-in person arranged the admin's lists: for each grid they have arranged, its columns in the order they put them (order; columns it does not name follow in the grid's own order) and the ones they switched off (hidden).

A grid they never arranged is absent and shows as the admin declares it. The person's own, the same in every organization they belong to. Read-only.

Access

Requires a signed-in session: The signed-in person's own layouts, read from their BetterAuth session; no path names anyone else

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

AI agent tool

No agent tool. How a person arranged the admin's grids is a display preference of the admin itself; the MCP server does not reach the auth service, and an agent reads records, not columns.

Connecting an agent: AI agents.

Example

curl

curl -X GET 'https://auth.getmanifold.io/api/auth/me/grid-layouts' \
  -H "Authorization: Bearer $MANIFOLD_TOKEN"

JavaScript (fetch)

const response = await fetch("https://auth.getmanifold.io/api/auth/me/grid-layouts", {
  method: "GET",
  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

{
  "layouts": [
    {
      "grid": "orders",
      "order": [
        "order",
        "customer",
        "status",
        "payment",
        "lines",
        "created",
        "reference",
        "source"
      ],
      "hidden": [
        "reference",
        "source"
      ],
      "updatedAt": "2026-10-22T02:31:40.000Z"
    }
  ]
}

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
`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
`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
`RequestLogUnavailable` tokenId, reason	The service could not record the request, so it did nothing.	Try again shortly.

How refusals work everywhere: Errors.

Used in

Page through the order book, arranged your way, step 6: Open the admin somewhere else