While most transactions are supported in both directions, we find it most efficient for the transaction originator to initiate the call. E.g. while we support an external party calling into our system to ‘Get Ship Request (940) from Spring’, we have found it faster and more efficient for our system to instead push the Ship Request (940) out to the receiving system (e.g. your WMS). Our system is the originator of the Ship Request (940) transaction so it is faster if we immediately push it out to the WMS (warehouse management system). Similarly, we prefer for the WMS to push back to us the completed shipment.
Request Parameters
Can filter on any of these. At least one is mandatory.
shipment_created
shipment_updated
po_num
shipment_num
shipment_ship_status
shipment_ship_open_date
shipment_ship_close_date
shipment_id
vendor_id
retailer_id
ship_to_location_id
Request Parameters Qualifiers
| Qualifier (key) | Description |
|---|---|
| eq | equal |
| neq | not equal |
| lt | less than |
| lte | less than or equal |
| gt | greater than |
| gte | greater than or equal |
| like | like |
| nlike | not like |
| in | in |
| nin | not in |
Request Parameters Format
Usage of one or more parameter qualifiers is mandatory.
shipment.filter.<qualifier>.<value>
example using more than one parameter...
https://api_user@api_key:portalapp.springsystems.com/api/ship-request-outgoing/export/ship_info.filter.gt.ship_info_created/2017-09-01T00:00:00Z/ship_info.filter.lt.ship_info_created/2017-09-25T14:28:35-0500