The Inventory server exposes three groups of endpoints:

All custom endpoints return JSON error bodies. OData endpoints follow the OData V4 error format.

Copy{
  "error": "Validation failed",
  "details": ["idempotencyKey is required", "docType must be one of PO, GRPO, Counting"]
}

Upload a scanned batch from App 1. Idempotent: re-uploading the same idempotencyKey updates the batch if it is in status Uploaded or Rejected, and silently ignores the re-upload if the batch is already past review (Approved, Posting, Posted, etc.).

CopyPOST /upload/batch
Content-Type: application/json
x-api-key: devkey123

{
  "idempotencyKey": "550e8400-e29b-41d4-a716-446655440000",
  "batchName":      "Delivery 2024-001",
  "docType":        "GRPO",
  "cardCode":       "V001",
  "warehouse":      "WH01",
  "docRef":         "DN-2024-001",
  "operator":       "john.doe",
  "sourceHost":     "WAREHOUSE-PC-01",
  "lines": [
    {
      "scannedBarcode": "5901234123457",
      "itemCode":       "ITEM-A",
      "itemName":       "Widget A",
      "quantity":       10,
      "uom":            "EA",
      "validationStatus": "OK"
    },
    {
      "scannedBarcode": "UNKNOWN-BAR",
      /* itemCode absent — validationStatus auto-set to Unresolved */
      "quantity":       2,
      "validationStatus": "Unresolved"
    }
  ]
}

Searches SAP B1 items by barcode, item code, or description. Proxied server-side to the SAP B1 Service Layer. Used by the web UI Item Search page. Requires an active session.

CopyGET /items/search?q=widget
Cookie: inv_sid=<session-id>

Copy{
  "value": [
    {
      "ItemCode":     "ITEM-A",
      "ItemName":     "Widget A",
      "BarCode":      "5901234123457",
      "InvntryUom":   "EA",
      "OnHand":       142
    }
  ]
}

Searches SAP B1 Business Partners of type Supplier. Used by the batch detail form to look up vendor card codes.

Copy{
  "value": [
    { "CardCode": "V001", "CardName": "Acme Supplies" }
  ]
}

Full OData V4 CRUD on batches. Base path: /odata/v4/batch/Batches

Copy# List all batches (top 20)
GET /odata/v4/batch/Batches?$top=20&$orderby=uploadedAt desc

# Filter by status and doc type
GET /odata/v4/batch/Batches?$filter=status eq 'Uploaded' and docType eq 'PO'

# Expand lines in a single request
GET /odata/v4/batch/Batches?$expand=lines

# Get a single batch with lines
GET /odata/v4/batch/Batches('<uuid>')?$expand=lines

Scanned lines within a batch. Always accessed via the parent batch expand or directly.

Copy# Lines for a specific batch
GET /odata/v4/batch/Lines?$filter=batch_ID eq '<uuid>'

# Unresolved lines across all batches
GET /odata/v4/batch/Lines?$filter=validationStatus eq 'Unresolved'

Custom actions are bound to the Batches entity. Call them via HTTP POST with the batch ID in the URL.

CopyPOST /odata/v4/batch/Batches('<uuid>')/inventory.approve
Content-Type: application/json

{ "comment": "Verified by supervisor" }

// Response 200
{ "value": { "status": "Approved" } }

CopyPOST /odata/v4/batch/Batches('<uuid>')/inventory.rejectBatch
Content-Type: application/json

{ "reason": "Wrong vendor code" }

// Response 200
{ "value": { "status": "Rejected" } }

CopyPOST /odata/v4/batch/Batches('<uuid>')/inventory.postToSap
Content-Type: application/json

{}

// Response 200 — success
{ "value": { "status": "Posted", "sapDocNum": 1042, "sapDocEntry": 37 } }

// Response 200 — failure (SAP rejected the document)
{ "value": { "status": "PostFailed", "error": "Item ITEM-X does not exist in company db" } }

How batch/line fields are mapped to SAP B1 document fields when posting.