...
| Info | ||
|---|---|---|
| ||
<Root> <input type="hidden" name="NEW_ITEM-DESCRIPTION[1]" value="CANON PowerShot SX430"/> <input type="hidden" name="NEW_ITEM-MATGROUP[1]" value="45121504"/> <input type="hidden" name="NEW_ITEM-QUANTITY[1]" value="1"/> <input type="hidden" name="NEW_ITEM-UNIT[1]" value="EA"/> <input type="hidden" name="NEW_ITEM-PRICE[1]" value="1393.00"/> <input type="hidden" name="NEW_ITEM-CURRENCY[1]" value="DKK"/> <input type="hidden" name="NEW_ITEM-VENDOR[1]" value=""/> <input type="hidden" name="NEW_ITEM-VENDORMAT[1]" value="1790C002AA"/> <input type="hidden" name="NEW_ITEM-CUST_FIELD1[1]" value="45121504"/> <input type="hidden" name="NEW_ITEM-CUST_FIELD2[1]" value="25.00"/> <input type="hidden" name="NEW_ITEM-CUST_FIELD3[1]" value="348.25"/> <input type="hidden" name="NEW_ITEM-LEADTIME[1]" value="9"/> </Root> |
Orders
Again, the formats vary, but xCBL 3.5/4.0 seems to be popular (or cXML if that is used for login).
We will give you the exact URL, but it will be similar to this: https://secure.webmercs.com/ibxwebservice/YOURSITE/ibxorder.ashx (It requires a valid order to be POSTed.)
We use SOAP for xCBL.
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding"> <SOAP-ENV:Header> <nseps:endpoints xmlns:nseps="urn:schemas-IBX:/docs/endpoint.nsendpoint" SOAP-ENV:mustUnderstand="true"> <nseps:to> <nseps:address></nseps:address> </nseps:to> <nseps:from> <nseps:address>TPID</nseps:address> </nseps:from> </nseps:endpoints> In your solution, you create a user email in the following format (added to the correct customer, of course): TPID@ibx-wmx.com You can set the TPID to anything you like. Orders from purchasing portals (where this solution is used today) normally use a GUID value, like 12bcd1dc-33e1-9000-a2ab-b1a873450102 (which would result in a user email = 12bcd1dc-33e1-9000-a2ab-b1a873450102@ibx-wmx.com), but you can use anything you want.
...
Keep in mind: 1) The TPID must match a user email in your system 2) The billing/shipping addresses must be valid 3) The products must exist in the solution
Value from OrderHeader/OrderParty/BuyerParty/Party/ListOfIdentifier/Identifier/Ident may be used in some cases.
Not punchout but "Catalog"?
...