Enhancements to GET API

With release 25C, WMS offers an enhanced support for your GET API requests by facilitating more entities and fields.

UPDATE OF DATE-TIME STANDARDS FOR THE ASYNCHRONOUS DATA EXTRACTION REST API

Now, when you perform a data extract using the Asynchronous Data Extraction REST API, the date-time fields will be displayed, as per the ISO 8601 standard.

The date will be in the format of YYYY-MM-DD. The time format is HH:MI:SS.FFZ.

NEW FIELD FOR THE INBOUND SHIPMENT DETAIL GET API

When you perform an ib_shipment_dtl GET API request, the Container ID information is required to accurately identify a record. So, now, you can easily look up the Container ID value via the newly exposed field “container_id”. You can also filter by the container ID via the “fields”/”values_list” function.

NEW ENTITIES FOR GET API REQUESTS 

ENTITY

FOR PAGINATED RESULTS

FOR NON-PAGINATED RESULTS (BY SPECIFIC ID)

* HEAD URL
serial_nbr_history GET .../lgfapi/v10/entity/ serial_nbr_history/

GET .../lgfapi/v10/entity/ serial_nbr_history/{id}
  • HEAD .../lgfapi/v10/entity/serial_nbr_history/
  • HEAD .../lgfapi/v10/entity/serial_nbr_history/{id}
cc_run GET .../lgfapi/v10/entity/cc_run/ GET .../lgfapi/v10/entity/cc_run/{id}
  • HEAD .../lgfapi/v10/entity/cc_run/
  • HEAD .../lgfapi/v10/entity/cc_run/{id}
ib_shipment_container_lock GET .../lgfapi/v10/entity/ib_shipment_container_lock/

GET .../lgfapi/v10/entity/ib_shipment_container_lock/{id}
  • HEAD .../lgfapi/v10/entity/ib_shipment_container_lock/
  • HEAD .../lgfapi/v10/entity/ib_shipment_container_lock/{id}
ib_shipment_vendor_perf GET .../lgfapi/v10/entity/ib_shipment_vendor_perf/ GET .../lgfapi/v10/entity/ib_shipment_vendor_perf/{id}

  • HEAD .../lgfapi/v10/entity/ib_shipment_vendor_perf/

  • HEAD .../lgfapi/v10/entity/ib_shipment_vendor_perf/{id}
invoice, invoice_dtl and invoice_dtl_history

  • GET .../lgfapi/v10/entity/invoice/

  • GET .../lgfapi/v10/entity/invoice_dtl/

  • GET .../lgfapi/v10/entity/invoice_dtl_history/

  • GET .../lgfapi/v10/entity/invoice/{id}

  • GET .../lgfapi/v10/entity/invoice_dtl/{id}

  • GET .../lgfapi/v10/entity/invoice_dtl_history/{id}
  • HEAD .../lgfapi/v10/entity/invoice/
  • HEAD .../lgfapi/v10/entity/invoice_dtl/
  • HEAD .../lgfapi/v10/entity/invoice_dtl_history/
  • HEAD .../lgfapi/v10/entity/invoice/{id}
  • HEAD .../lgfapi/v10/entity/invoice_dtl/{id}
  • HEAD .../lgfapi/v10/entity/invoice_dtl_history/{id}
item_pre_pack

GET .../lgfapi/v10/entity/item_pre_pack/

 GET .../lgfapi/v10/entity/item_pre_pack/{id}
  • HEAD .../lgfapi/v10/entity/item_pre_pack/
  • HEAD .../lgfapi/v10/entity/item_pre_pack/{id}
movement_request_serial_nbr GET .../lgfapi/v10/entity/movement_request_serial_nbr/ GET .../lgfapi/v10/entity/movement_request_serial_nbr/{id}
  • HEAD .../lgfapi/v10/entity/movement_request_serial_nbr/
  • HEAD .../lgfapi/v10/entity/movement_request_serial_nbr/{id}

* HEAD URL is used to validate if an object exists for the entity.

DEPRECATION OF FLAGS IN SCHEDULED JOBS

The "Encrypt" and "Decrypt" flags in the Scheduled Job for "Copy Files" are no longer supported for any newly created jobs (using the "Create" button). However, it will continue to be available if you use "Edit" and copy the existing jobs.

Steps to Enable

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > APIs & Schema). If you are new to Oracle's REST services you may want to begin with the Quick Start section.