Skip to content
Logistics systems of record

Logistics systems of record

Order, transport, warehouse, yard and inventory management systems are read by one REST implementation, parameterised by system. Across these systems, what differs is the default resource and the vendor’s paging and filter dialect. Those differences are data, not separate connectors.

Systems and type spellings

SystemType spellingsDefault resourceChanged-since parameterDefault lookback
OMS (orders)oms, ordermanagementordersupdatedSince1,440 min
WMS (warehouse)wms, warehousemanagementinventorymodifiedAfter240 min
WHS (warehouse receipts)whs, warehousereceiptsmodifiedAfter1,440 min
YMS (yard)yms, yardmanagementappointmentsupdatedSince720 min
TMS (transport)tms, transportmanagementshipmentsupdatedSince1,440 min
IMS (inventory)ims, inventory, inventorymanagementinventorymodifiedAfter240 min
FMS (fleet)fms, fleetmanagementassetsmodifiedAfter1,440 min
DPS (demand planning)dps, demandplanningforecastsupdatedSince10,080 min
RPS (route planning)rps, routeplanning, routeoptimizationrouteplansupdatedSince1,440 min
UAS (drone fleet)uas, drone, dronefleetmissionsupdatedSince240 min
Genericlogisticsapi, logisticsfrom system——

With the generic logisticsapi type, the system comes from the config’s system field. The default paging parameters are limit, offset and cursor.

Provider dialects

Setting provider changes the paging and changed-since parameters:

providerChanged-sincePage sizeOffset / cursor
project44updatedAfterperPageoffset
fourkitessincepage_sizepage_token
manhattanlastUpdatedSincesizepage
blue_yondermodifiedSincepageSize—
ibm_sterlingmodifyTsFrommaximumRecords—
netsuitelastModifiedDatelimitoffset
oracleLastUpdateDatelimitoffset
generic or emptythe system’s defaults

Settings (LogisticsAPIConnectionConfig)

SettingMeaning
systemoms, wms, whs, yms, tms, ims (and the other systems above)
providerThe vendor dialect (see above)
base_urlAn http:// or https:// URL. Required.
resourceThe resource path to read. Empty uses the system default.
site_idWarehouse, yard or DC scope
auth_modeapi_key (default), bearer, basic, oauth2_client_credentials or none
api_key_headerThe API-key header. Default X-API-Key.
token_url, scopeFor oauth2_client_credentials
page_sizeDefault 200, maximum 1,000
max_recordsDefault 5,000, maximum 50,000
lookback_minutesChanged-in window. Default is per system, maximum 90 days.

Older connections that were stored with the per-system messages (OMSConnectionConfig, WHSConnectionConfig, TMSConnectionConfig, YMSConnectionConfig, InventoryConnectionConfig) are still read:

  • Their base_url is used.
  • system_type or provider becomes the provider.
  • warehouse_id or yard_id becomes the site.

Every setting can also be given as a connection property (base_url, resource, site_id, provider, auth_mode, …).

Credentials by auth_mode

auth_modeCredential keys
api_keyapi_key (also apikey, token, access_token), sent in api_key_header
bearertoken (also bearer_token, access_token, api_key)
basicusername and password
oauth2_client_credentialsclient_id and client_secret. The token is cached until shortly before it expires.
none—

Behaviour

  • Test requests the target resource with a page size of 1, within 15 s. A success means the API answered and accepted the credential.
  • Execute pages through the resource:
    • Within the record cap, at most 200 pages, and a 3-minute budget.
    • Each page is capped at 16 MiB.
    • Redirects are followed on the same host only, up to 5.
    • Rows are the records as the API returns them. The columns are the union of fields seen across the rows. An empty result is reported as Success=false: <SYSTEM> connector reached … and received no records.
  • Explore returns supported=false. These systems publish no common catalogue.
  • Internal addresses are allowed by default. Set allow_internal_network=false for a public API.