Warehouse (WHS)
change-me is every test credential. They are still encrypted and still ask for a login, because FACE refuses a connection that is not (see Connector security). Use a scratch machine or a scratch cluster.Grade D · dataset: API (the vendor’s response payloads) · type whs
What it is
A warehouse system of record, read over REST, one connection per warehouse. In the test estate it holds warehouse tasks. The connector reference is Logistics systems of record.
Grade
D. Dataset and model: the quickstart dataset and its expected model ship. There is no vendor system to stand up for this type; load the dataset and fetch it.
See the grade table for all 32 types.
Settings and credentials
From the connection catalogue. Settings are ordinary fields on the connection record. Credentials are kept in a sealed bundle and never returned.
| Names | |
|---|---|
| Type | whs |
| Settings | base_url, warehouse_id |
| Credentials | api_key |
The test connection
The test estate defines 3 connections of this type. The first is shown, and expected.json lists every one.
Warehouse WH-NORTH
| Setting | Test value |
|---|---|
base_url | https://whs.quillmere.invalid/api |
warehouse_id | WH-NORTH |
Credentials: api_key. In the test estate, every credential is change-me. Credentials are write-only: they go into the sealed credential bundle and are never returned.
Stand up the test system
The safety rule at the top of this page comes first: a scratch machine or a scratch cluster, never a production or platform one.
- Download
whs.zipand unzip it. It holds paginated REST responses in a generic shape, andexpected.json. These types are for a customer’s own systems of record, so no vendor is imitated. - There is no system to stand up from this bundle. Load the records into the system of record you want to test against, or open them next to
expected.json. - Add the connection with the settings above, pointed at that system’s base URL.
What FACE finds
FACE fetches these records over its logistics REST connector, which pages through the system’s resource. It reads no catalogue, so the expected model is the record shape.
| Dataset | Kind | Domain | Primary key | Rows | Fields |
|---|---|---|---|---|---|
tasks | rest_resource | warehouse_ops | task_id | 24 | 10 |
facility | rest_resource | warehouse_ops | warehouse_id | 3 | 11 |
expected.json in the download has the full model: every field with its logical type, the source’s native type and nullability.
How it joins the Quillmere universe
This source carries 5 of the universe’s shared keys. The same ID means the same thing in every source: a shipment here is the same shipment in the database, the event bus, the GPS track and the claim PDF.
| Universe entity | Fields here | Also in |
|---|---|---|
| asn | tasks.asn_id | logisticsapi, postgres |
| dock | tasks.dock_id | cctv, excel, files, kafka, logisticsapi, postgres, sensorgateway, yms |
| role | tasks.assigned_role | servicenow, sharepoint, yms |
| shipment | tasks.shipment_id | bigquery, d365, databricks, document, excel, files, github, guidewire, iot, kafka, logisticsapi, mqtt, mysql, objectstore, postgres, redshift, salesforce, sap, servicenow, sharepoint, tms, yms |
| warehouse | facility.warehouse_id, tasks.warehouse_id | inventory, oms, postgres, redshift, tms, yms |
It holds no evidence for the six planted anomalies. It is context: it makes the shared keys resolve.
See all connectors at once for the walkthrough across every source.
Download
whs.zip: 7 files,expected.jsonincluded.
This is one of 25 zips: the 7 streaming types ship as replay recordings instead.
What is in the zip
whs/api_tasks_WH-NORTH.jsonwhs/api_facility_WH-NORTH.jsonwhs/api_tasks_WH-EAST.jsonwhs/api_facility_WH-EAST.jsonwhs/api_tasks_WH-SOUTH.jsonwhs/api_facility_WH-SOUTH.jsonwhs/expected.json
The whole universe is universe.json. manifest.json lists every download with its size and SHA-256, and SHA256SUMS is the same list for sha256sum -c.