Order Change APIs
Was this helpful?
Was this helpful?
The change, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
Use limit parameter to change the number of returned messages and combine it with offset to traverse down the list, e.g:
To get new messages only, use the "Get incoming read orderchanges" endpoint instead.
""""""""""YYYY-MM-DD, e.g. 2024-01-01
""YYYY-MM-DD, e.g. 2024-01-01
""YYYY-MM-DD, e.g. 2024-01-01
""YYYY-MM-DD, e.g. 2024-01-01
""""""Either "application/json" (default) or "application/xml"
""APIs related to order change handing
Order Change is part of Advanced Ordering 3.0:
Message Syntax:
""""""Either "application/json" (default) or "application/xml"
""APIs related to order change handing
Order Change is part of Advanced Ordering 3.0:
Message Syntax:
""""Either "application/json" (default) or "application/xml"
""The change, in JSON, will always include the three latest messages, per default. Using XML you always only get one (as there's no "array" function for XML).
Use limit parameter to change the number of returned messages and combine it with offset to traverse down the list, e.g:
To get new messages only, use the "Get outgoing read orderchanges" endpoint instead.
""""Either "application/json" (default) or "application/xml"
""APIs related to order change handing
Order Change is part of Advanced Ordering 3.0:
Message Syntax:
""""""Either "application/json" (default) or "application/xml"
""