Dismiss one card from the caller's own dashboard

PUT /dashboard/dismissals/{widget}

widget is the card's key: its kind (sales-trend, top-mover, connect-channel, invite-team) or its kind and subject (top-mover:WIDGET-1), so hiding today's top mover does not hide the next one. Appends reporting.widget-dismissed and answers the layout as it reads afterwards. Idempotent by state: a card is dismissed once, so dismissing one already dismissed appends nothing and answers the same layout.

Access

Requires a signed-in session: the dismissal is the caller's own, keyed by the verified session user

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

Retries

Idempotent by state: a card is dismissed once, so dismissing one already dismissed appends nothing and answers the same layout.

Why every write carries a key: Idempotency and retries.

Facts appended

reporting.widget-dismissed

What a fact is: Facts and the journal.

AI agent tool

No agent tool. Hiding a card on a person's own admin home screen is that person's click in the admin, not an agent's action.

Connecting an agent: AI agents.

Example

curl

curl -X PUT 'https://reporting.getmanifold.io/dashboard/dismissals/sales-trend' \
  -H "Authorization: Bearer $MANIFOLD_TOKEN"

JavaScript (fetch)

const response = await fetch("https://reporting.getmanifold.io/dashboard/dismissals/sales-trend", {
  method: "PUT",
  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

{
  "userId": "usr_01a12e7b-6080-7a3c-a1fc-94dbc33aeadb",
  "dismissed": [
    "sales-trend"
  ]
}

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: reporting-manager.openapi.json. Base URL https://reporting.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
`DashboardNeedsPerson` userId	A home dashboard belongs to a person, and this token is not one.	Call it signed in as a person.
`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.	Send the same request again shortly.

How refusals work everywhere: Errors.

Used in

Read the dashboard and tidy it, step 6: Dismiss a card
Read the dashboard and tidy it, step 7: Dismiss it again