Topolo Docs Topolo Platform
Open workspace

Get Inventory location

Read one granted-workspace location by its returned identifier, with normalized code, default flag and timestamps. This response contains no per-location stock totals.

Outcome

Read one granted-workspace location by its returned identifier, with normalized code, default flag and timestamps. This response contains no per-location stock totals.

Before you start

  • Verify the authenticated identity, exact environment and pinned approved organization context before preparing an action.
  • The published application permission is workspace:read. Discover a granted Inventory workspace and bind that exact resource. Supplied identifiers do not grant access.

Discover the target

topolo whoami --json
topolo actions get app_topolo_inventory.locations.get --detail --json
topolo resources topolo-inventory --json
topolo workspaces list topolo-inventory --json
  • Select the exact granted workspace id as INVENTORY_WORKSPACE_ID. Fixture ids authorize no live operation.
  • Discover location ids through locations.list or the reviewed locations.create response in this workspace.

Request

GET /api/locations/{locationId}

Save action input as payload.json. Inspect the plan for the exact path, query and body. Set INVENTORY_WORKSPACE_ID from granted resource discovery.

Inspect and test this action in the signed action console, then perform the verification below.

Input fields

FieldRequiredTypeConstraints
locationIdRequiredstringExisting location id returned by locations.list or locations.create.; {"minLength":1}

View the complete input schema in the action console. The same schema is available through CLI and MCP action discovery.

Effects

  • Reads one organization/workspace-scoped location without mutation.

Interpret the response

Use response path $.location.id for inventory_location. An empty list does not discover a target.

Match location.id to the discovered input id. Do not infer a stock balance or canonical workspace identity from this location projection.

The success schema was checked against captured handler responses. Delegated Auth profile and canonical widget context fields can vary; exact Inventory projections and all six raw SQL export stores are source-reviewed. Error examples retain their actual refusal shapes.

View the complete success schema in the action console. The worked examples below retain complete captured responses; action discovery supplies the exact schema.

Worked examples

Captured exported Worker responses use both real local SQLite D1 databases with all six committed migrations, synthetic Auth/workspace grants and simulated Notify/Nexus/archive transport. They prove local handler shapes and scoped behavior, not live authorization, notification delivery, metering acceptance or environment deployment. Large 100-row list/capped-dashboard captures are retained in local evidence; committed tests verify those limits while worked guides use smaller complete responses. Refused examples demonstrate boundaries and must not be executed as successful workflows.

Successful request

Actual exported Worker response with both local SQLite D1 databases and all committed migrations; synthetic Auth/grants and simulated Notify/Nexus/archive transport. No live delivery, billing or environment deployment proof. Captured scenario: locations.get.

Input · payload.json:

{
  "locationId": "invloc_c3564dea-5bd0-4a93-bf00-aa25b17fd78c"
}

CLI:

topolo actions validate app_topolo_inventory.locations.get --data @payload.json --json
topolo actions plan app_topolo_inventory.locations.get --resource-type workspace --resource-id "$INVENTORY_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_inventory.locations.get --resource-type workspace --resource-id "$INVENTORY_WORKSPACE_ID" --data @payload.json --json

MCP tool and arguments:

{
  "tool": "topolo_read_action",
  "arguments": {
    "actionId": "app_topolo_inventory.locations.get",
    "input": {
      "locationId": "invloc_c3564dea-5bd0-4a93-bf00-aa25b17fd78c"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by granted resource discovery>"
  }
}

Captured local response · HTTP 200:

{
  "location": {
    "id": "invloc_c3564dea-5bd0-4a93-bf00-aa25b17fd78c",
    "name": "Main warehouse",
    "code": "main",
    "isDefault": true,
    "createdAt": "2026-10-04T05:46:36.666Z",
    "updatedAt": "2026-10-04T05:46:36.666Z"
  }
}

HTTP 200. Match location.id to the discovered input id. Do not infer a stock balance or canonical workspace identity from this location projection.

Refused request · HTTP 404

Actual exported Worker response with both local SQLite D1 databases and all committed migrations; synthetic Auth/grants and simulated Notify/Nexus/archive transport. No live delivery, billing or environment deployment proof. Captured scenario: missing location.

Input · payload.json:

{
  "locationId": "invloc_missing"
}

CLI:

topolo actions validate app_topolo_inventory.locations.get --data @payload.json --json
topolo actions plan app_topolo_inventory.locations.get --resource-type workspace --resource-id "$INVENTORY_WORKSPACE_ID" --data @payload.json --json

Captured local response · HTTP 404:

{
  "error": "not_found"
}

HTTP 404. The handler refused this request. Resolve its exact cause before retrying; input validation can reject an invalid fixture before it reaches the handler.

Verify the result

  • Match location.id to the discovered input id.
  • Do not infer a stock balance or canonical workspace identity from this location projection.

Errors and recovery

  • invalid_action_input (HTTP 400): Correct only the exact fields reported by the published schema validator. An invalid input can be refused before its handler.
  • action_permission_required (HTTP 403): Stop when the verified credential lacks the published action permission. Resource identifiers and organization ownership do not grant that permission.
  • organization_required (HTTP 403): Use the specifically authorized organization context; personal scope cannot act on organization-owned Inventory data.
  • workspace_required (HTTP 400): Discover an authorized Inventory workspace and pass its exact separate resource binding; bootstrap does not select a workspace.
  • workspaces_unavailable (HTTP 503): Retain the request id and report unavailable canonical workspace discovery; do not invent a default workspace.
  • not_found (HTTP 404): Discover the resource through the appropriate authorized list or creation response; a foreign or absent identifier is not accessible.

Auth, action-input validation and platform resource resolution can refuse a request before its handler. Retain the exact error, request id and context; requesting another context is not a legitimate way to bypass a refusal.

Recovery boundary

The read does not change local inventory records. No local rollback is needed; do not perform a mutation merely to reverse a read.

  • Record Inventory stock movement: Append one nonzero signed quantity delta against an active item and existing location in the same workspace. Movement type labels do not set the sign, pair a transfer or defer stock while review is pending.

Evidence

Captured exported Worker responses use both real local SQLite D1 databases with all six committed migrations, synthetic Auth/workspace grants and simulated Notify/Nexus/archive transport. They prove local handler shapes and scoped behavior, not live authorization, notification delivery, metering acceptance or environment deployment. Large 100-row list/capped-dashboard captures are retained in local evidence; committed tests verify those limits while worked guides use smaller complete responses. Capture digests and test scenarios are retained in the source fixture records.