post
https://api.shipmonk.com/v1/integrations/receiving
General description
- ERP push to ShipMonk
items.[].lotor any of its property can be null
ASN & Receiving Key
- When updating a Receiving, the identifying properties are
receiving_keyandasnin this order.- In case both are supplied
- First, Receiving is retrieved by
receiving_key. If found, it is updated with new ASN if current ASN is different thanasnin the request body. - If not found, Receiving is retrieved by
asn. If found, it is updated with newreceiving_keyin the request body. - If not found, new Receiving is created with
receiving_keyand asn being its unique identifiers.
- First, Receiving is retrieved by
- In case only asn is supplied
- First, Receiving is retrieved by
asn. If found,receiving_keyof the Receiving is left as-is as it cannot be deleted upon setting up. - If not found, new Receiving is created with
asnbeing its unique identifier.
- First, Receiving is retrieved by
- In case only
receiving_keyis supplied- The request is rejected, as
asnis required field.
- The request is rejected, as
- In case both are supplied
LineKey
- When item objects are supplied with
line_keystring field, these items are then uniquely identified and can be referenced by it, if needed to change expected quantity. - Line Key must be unique per receiving.
- Null/missing values are also expected. Such lines are then grouped by product and lot if supplied multiple times in the POST request.
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…