Get focused dashboard

Outcome

Reads one accessible dashboard in the active ownership context without changing data.

Before you start

• Verify the intended environment, authenticated identity and explicitly authorized ownership context.
• Discover the published dashboard:read permission and any required resource grant.

Discover the target

topolo whoami --json
topolo actions get app_topolo_one.dashboard_layouts.get --detail --json

• id: Exact identifier retained from the corresponding create response or permitted list; dashboard ids and local application ids are distinct.

Request

GET /api/dashboard-layouts/{id}

Inspect and test this action.

Input fields

Inspect nested fields.

Interpret the response

Confirm the returned id, ownership scope and visibility match the intended dashboard.

Inspect the declared output schema and captured variants.

Worked examples

Actual exported One Worker with local Miniflare D1/KV. Authentication, application discovery, checkout, billing and remote widget providers are controlled synthetic responses; outbound access is sealed. No live provider outcome is established.

Save the reviewed input below as payload.json; substitute discovered identifiers and bind credential/resource context separately. CLI:

topolo actions validate app_topolo_one.dashboard_layouts.get --data @payload.json --json
topolo actions plan app_topolo_one.dashboard_layouts.get --data @payload.json --json
topolo actions call app_topolo_one.dashboard_layouts.get --data @payload.json --detail --json

MCP planning and execution use the same reviewed input:

{
  "tool": "topolo_prepare_action",
  "arguments": {
    "actionId": "app_topolo_one.dashboard_layouts.get",
    "input": {
      "id": "dashboard_c601634a-eaba-43fb-bfe6-99ca40878d4c"
    }
  }
}

{
  "tool": "topolo_read_action",
  "arguments": {
    "actionId": "app_topolo_one.dashboard_layouts.get",
    "input": {
      "id": "dashboard_c601634a-eaba-43fb-bfe6-99ca40878d4c"
    },
    "detail": true
  }
}

Refused request · HTTP 403 · organization_scope_forbidden

Input · payload.json:

{
  "id": "dashboard_96cee461-3ae7-4acb-aad7-baf038ca5f8e"
}

Captured response:

{
  "error": "organization_scope_forbidden"
}

Select a dashboard visible in the active organization context.

Successful response · HTTP 200

Input · payload.json:

{
  "id": "dashboard_c601634a-eaba-43fb-bfe6-99ca40878d4c"
}

Captured response:

{
  "data": {
    "dashboard": {
      "id": "dashboard_c601634a-eaba-43fb-bfe6-99ca40878d4c",
      "ownerUserId": "user_int_1",
      "organizationId": "org_int_1",
      "scopeType": "organization",
      "scopeId": "org_int_1",
      "name": "Fixture operations",
      "description": "",
      "purpose": "custom",
      "timeContext": {
        "range": "30d",
        "comparison": "none",
        "timezone": "UTC"
      },
      "visibility": "private",
      "isDefault": true,
      "contributions": [],
      "analyses": [],
      "sharedUserIds": [],
      "canEdit": true,
      "createdAt": "2026-10-06T01:43:23.046Z",
      "updatedAt": "2026-10-06T01:43:23.046Z"
    }
  }
}

Confirm the returned id, ownership scope and visibility match the intended dashboard.

Refused request · HTTP 401 · auth_error

Input · payload.json:

{
  "id": "dashboard_3baf8d10-8eb7-4ae1-9cac-95aa398a0595"
}

Captured response:

{
  "error": "Token validation failed"
}

Authenticate using the required credential type for this action; service-only actions require the registered Auth service identity.

Verify the result

• Confirm the returned id, ownership scope and visibility match the intended dashboard.

Errors and recovery

• personal_context_required (HTTP 403): Switch to the dashboard's Personal context. Owning a private dashboard does not bypass the active context boundary.
• organization_scope_forbidden (HTTP 403): Select a dashboard visible in the active organization context.
• auth_error (HTTP 401): Authenticate using the required credential type for this action; service-only actions require the registered Auth service identity.

These are observed local refusals; inspect the raw error body because one SDK code can represent several handler messages. Preserve the request id when available.

Recovery boundary

This read changes no saved dashboard.

Evidence

Actual exported One Worker with local Miniflare D1/KV. Authentication, application discovery, checkout, billing and remote widget providers are controlled synthetic responses; outbound access is sealed. No live provider outcome is established.