Document type: Order confirmation

The client fetches all order confirmations via the following request:

https://b2b.beispielserver.com/?RequestName=OrderConfirmationQueryRequest&BuyersID=B127645&Password=secret

The server's response could appears as follows - even if this is somewhat unrealistic at present (only two order confirmations within one year):

<?xml version="1.0" encoding="utf-8" ?> <OrderConfirmationQueryResponse xmlns="urn:veloconnect:receipt-1.3" xmlns:vct="urn:veloconnect:transaction-1.0" xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-1.0"> <vct:BuyersID>B127645</vct:BuyersID> <vct:ResponseCode>200</vct:ResponseCode> <OrderConfirmationHeader> <OrderConfirmationID>B2018001</OrderConfirmationID> <cbc:IssueDate>2018-10-15</cbc:IssueDate> <Description>Vororder 2019</Description> </OrderConfirmationHeader> <OrderConfirmationHeader> <OrderConfirmationID>B2019001</OrderConfirmationID> <cbc:IssueDate>2019-08-27</cbc:IssueDate> <OrderID>B2019001</OrderID> </OrderConfirmationHeader> </OrderConfirmationQueryResponse>

In this case, we would have obtained the same result using one of the following requests:

https://b2b.beispielserver.com/?RequestName=OrderConfirmationQueryRequest&BuyersID=B127645&Password=secret&OrderConfirmationID=B201

 

 We now query these two order confirmations with:

and receive the following response, for example: