Asset Interface

The Asset JSON Interface allows you to submit Asset data in JSON format into the existing stage table. The API validates all passed values (per the provided specification files) and either processes the data synchronously or queues it for asynchronous processing depending on the async_flg.

URL

POST .../wms/lgfapi/v10/stage/asset

Request Parameters

Section	Name	Type	Required	Description
stage_asset_list	asset_nbr	String	Yes	Unique identifier for the asset. Must follow the format/length rules defined in the specification.
	action_code	String	Yes	Action to perform on the asset. Allowed values typically include CREATE, UPDATE, DELETE (refer to interface spec).
	lpn_type	String	Yes	License Plate Number (LPN) type associated with the asset. Must be valid in WMS configuration.

Request Body

{
    "async_flg":false,
    "header": {
		 "document_version": "25D",
                 "origin_system": "Host",
                 "client_env_code": "QA",
                 "parent_company_code": "QATSTPC",
                 "entity": "asset",
                 "timestamp": "2025-01-14 12:12:12",
                 "messageid": "lgf_asset",
                 "facility_code": "QATST01",
                 "company_code": "QATSTPC"   
              }, 
    "stage_asset_list": [
                                    {    
                                        "asset_nbr": "ASSETNBR01",
                                        "action_code": "CREATE",
                                        "lpn_type": "LPNTW01"
                                     }                              
                              ]
}

Note:

• The list allows multiple assets in a single call.
• All mandatory fields must be present; non-mandatory fields may be included as required.
• Validation rules are applied exactly as specified in:
  • Asset_required.json: mandatory fields
  • Asset_All.json: full field catalog
  • Interface specification: allowed values, enumerations, formats

• Behavior

• Accepts Asset payloads in JSON format and loads them into the stage table.
• API can run in synchronous or asynchronous mode based on async_flg.
• System validates all passed values and returns clear error messages on validation failure.
• Mandatory fields (from Asset_required.json) must be provided. Non-mandatory fields are optional.
• Full field details and allowed values should be taken from Asset_All.json and the interface specification.

Sample Response

200 OK