The facts behind one leaf cell of a saved report

GET /report-runs/drill

The facts behind one leaf cell of a saved report: the distinct fact rows that summed into measure for the leaf group key (a JSON array with one value per grouping), each with its stable row id and the journal evt_ ids it was folded from — the drill-through trail back to the exact facts.

Read-only, gated by the same job visibility as the run. Requires the analyse, account or admin job.

Access

Requires reports:read.

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

AI agent tool

Agents call this as reporting_drill_report (Reporting: Drill report), in the reporting toolset. It only reads.

Connecting an agent: AI agents.

Example

curl

curl -X GET 'https://reporting.getmanifold.io/report-runs/drill?reportId=rpt_01a1586d-1d4c-7444-8444-444444444444&measure=quantity&key=%5B%22WIDGET-BLUE%22%5D' \
  -H "Authorization: Bearer $MANIFOLD_TOKEN"

JavaScript (fetch)

const response = await fetch("https://reporting.getmanifold.io/report-runs/drill?reportId=rpt_01a1586d-1d4c-7444-8444-444444444444&measure=quantity&key=%5B%22WIDGET-BLUE%22%5D", {
  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

{
  "measure": "quantity",
  "key": [
    "WIDGET-BLUE"
  ],
  "value": 40,
  "rows": [
    {
      "entity": "stockMovement",
      "id": "mov_01a13891-2a00-7d4e-ac17-9d606148e08b",
      "eventIds": [
        "evt_01a13891-2a00-7d4e-ac17-9d606148e08c"
      ]
    }
  ]
}

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.

`400`

Refusal	What it means	What to do
`ReportDefinitionRefused` refusals	The report definition is not valid. `refusals` lists each problem.	Fix each one and send it again.

`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
`ReportFieldsForbidden` refusals	The report reads fields your roles may not see. `refusals` names them.	Leave those fields out, or ask for a role that sees them.
`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.

`404`

Refusal	What it means	What to do
`ReportNotFound` reportId	No such record in this organization.	Check the id in the path or the body.

`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

Build, save and run a report, step 7: Drill a cell