Review Inventory stock movement

Resolve a pending movement review as approved or rejected. This changes review metadata only: rejecting does not delete the ledger entry, reverse stock or undo notifications already emitted.

Outcome

Resolve a pending movement review as approved or rejected. This changes review metadata only: rejecting does not delete the ledger entry, reverse stock or undo notifications already emitted.

Before you start

Verify the authenticated identity, exact environment and pinned approved organization context before preparing an action.
The published application permission is workspace:write. Discover a granted Inventory workspace and bind that exact resource. Supplied identifiers do not grant access.
Authorize the documented inventory, review, import, notification, metering, privacy or archival effects before CLI --confirm or MCP confirm:true.

Discover the target

topolo whoami --json
topolo actions get app_topolo_inventory.movements.review --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.
Use the pending movement id saved from movements.create or the latest-100 movements.list response; do not guess a historical id.

Request

POST /api/movements/{movementId}/review

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

Field	Required	Type	Constraints
`movementId`	Required	string	Existing pending movement id from the creation response or recent movement list.; {"minLength":1}
`decision`	Required	string	Exactly approved or rejected. Rejection changes metadata and does not reverse stock.; {"enum":["approved","rejected"]}

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

Effects

Checks that the scoped row exists and is pending, then records the decision, reviewing user and current timestamp.
Review status does not change quantityDelta or aggregate stock; no notification or usage emission is performed by this handler.

Interpret the response

The review response contains ok, decision and reviewedAt, with no movementId. Use authorized input.movementId for separate list verification.

Verify review.decision and reviewedAt, then locate input.movementId through the recent movements list when still within its 100-row window. An already resolved or not_required row returns 409 review_not_pending. Read items.get to confirm rejection did not reverse stock.

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: movements.review.

Input · payload.json:

{
  "movementId": "invmove_16afb7cb-6c3f-4051-a68e-3988135bf040",
  "decision": "approved"
}

CLI:

topolo actions validate app_topolo_inventory.movements.review --data @payload.json --json
topolo actions plan app_topolo_inventory.movements.review --resource-type workspace --resource-id "$INVENTORY_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_inventory.movements.review --resource-type workspace --resource-id "$INVENTORY_WORKSPACE_ID" --data @payload.json --confirm --json

MCP tool and arguments:

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_inventory.movements.review",
    "input": {
      "movementId": "invmove_16afb7cb-6c3f-4051-a68e-3988135bf040",
      "decision": "approved"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by granted resource discovery>",
    "confirm": true
  }
}

Captured local response · HTTP 200:

{
  "review": {
    "ok": true,
    "decision": "approved",
    "reviewedAt": "2026-10-04T05:46:37.232Z"
  }
}

HTTP 200. Verify review.decision and reviewedAt, then locate input.movementId through the recent movements list when still within its 100-row window. An already resolved or not_required row returns 409 review_not_pending. Read items.get to confirm rejection did not reverse stock.

Another supported request

Input · payload.json:

{
  "movementId": "invmove_9515c62a-e304-4bf5-84c1-d5ec3b020789",
  "decision": "approved"
}

CLI:

topolo actions validate app_topolo_inventory.movements.review --data @payload.json --json
topolo actions plan app_topolo_inventory.movements.review --resource-type workspace --resource-id "$INVENTORY_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_inventory.movements.review --resource-type workspace --resource-id "$INVENTORY_WORKSPACE_ID" --data @payload.json --confirm --json

MCP tool and arguments:

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_inventory.movements.review",
    "input": {
      "movementId": "invmove_9515c62a-e304-4bf5-84c1-d5ec3b020789",
      "decision": "approved"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by granted resource discovery>",
    "confirm": true
  }
}

Captured local response · HTTP 200:

{
  "review": {
    "ok": true,
    "decision": "approved",
    "reviewedAt": "2026-10-04T05:46:38.238Z"
  }
}

Another supported request

Input · payload.json:

{
  "movementId": "invmove_3847adc5-c5b0-452d-87a0-37b1272057be",
  "decision": "rejected"
}

CLI:

topolo actions validate app_topolo_inventory.movements.review --data @payload.json --json
topolo actions plan app_topolo_inventory.movements.review --resource-type workspace --resource-id "$INVENTORY_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_inventory.movements.review --resource-type workspace --resource-id "$INVENTORY_WORKSPACE_ID" --data @payload.json --confirm --json

MCP tool and arguments:

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_inventory.movements.review",
    "input": {
      "movementId": "invmove_3847adc5-c5b0-452d-87a0-37b1272057be",
      "decision": "rejected"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by granted resource discovery>",
    "confirm": true
  }
}

Captured local response · HTTP 200:

{
  "review": {
    "ok": true,
    "decision": "rejected",
    "reviewedAt": "2026-10-04T05:46:37.164Z"
  }
}

Refused request · HTTP 404

Input · payload.json:

{
  "movementId": "invmove_missing",
  "decision": "approved"
}

CLI:

topolo actions validate app_topolo_inventory.movements.review --data @payload.json --json
topolo actions plan app_topolo_inventory.movements.review --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.

Refused request · HTTP 409

Input · payload.json:

{
  "movementId": "invmove_24b33b0b-2f8a-4bdc-a627-f69bf24413a9",
  "decision": "approved"
}

CLI:

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

Captured local response · HTTP 409:

{
  "error": "review_not_pending"
}

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

Refused request · HTTP 409

Input · payload.json:

{
  "movementId": "invmove_3847adc5-c5b0-452d-87a0-37b1272057be",
  "decision": "approved"
}

CLI:

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

Captured local response · HTTP 409:

{
  "error": "review_not_pending"
}

HTTP 409. 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

Verify review.decision and reviewedAt, then locate input.movementId through the recent movements list when still within its 100-row window.
An already resolved or not_required row returns 409 review_not_pending. Read items.get to confirm rejection did not reverse stock.

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.
review_not_pending (HTTP 409): Only pending reviews can be resolved. Do not retry a resolved or not_required row as a different decision.
review_decision_invalid (HTTP 400): Use the exact approved or rejected enum; input validation normally refuses other values first.

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

No published review-reset or decision-edit action exists. An authorized stock correction is a separate compensating movement, not a review retry.

List Inventory stock movements: Read up to 100 newest ledger entries in the granted workspace, enriched with item/location labels. Every review state is included and there is no cursor or full-ledger export on this action.
Get Inventory item: Read one item in the granted workspace with descriptive fields, archive status and quantityOnHand computed from all its movements. Archived items remain readable; missing or foreign items return not_found.
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.

Review Inventory stock movement

Outcome

Before you start

Discover the target

Request

Input fields

Effects

Interpret the response

Worked examples

Successful request

Another supported request

Another supported request

Refused request · HTTP 404

Refused request · HTTP 409

Refused request · HTTP 409

Verify the result

Errors and recovery

Recovery boundary

Related actions

Evidence