Document_type: Offer

The request

https://b2b.beispielserver.com/?RequestName=OfferQueryRequest&BuyersID=B127645&Password=secret&FromDate=2019-08-01&RequestReference=SONDERANGEBOT

receives the following server response, for example:

<?xml version="1.0" encoding="utf-8" ?>
<OfferQueryResponse 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>
 <OfferHeader>
   <OfferID>O1234</OfferID>
   <cbc:IssueDate>2019-09-15</cbc:IssueDate>
   <RequestReference>SONDERANGEBOT-2019-09</RequestReference>
 </OfferHeader>
 <OfferHeader>
   <OfferID>O1235</OfferID>
   <cbc:IssueDate>2019-08-15</cbc:IssueDate>
   <RequestReference>SONDERANGEBOT-2019-08</RequestReference>
 </OfferHeader>
</OfferQueryResponse>

If the server supported XML-POST(-S), the request could also have been realized via a POST of the following body:

<?xml version="1.0" encoding="utf-8" ?>
<OfferQueryRequest 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:Credential><vct:Password>secret</vct:Password></vct:Credential>
   <DateRange>
       <FromDate>2019-08-01</FromDate>
   </DateRange>
   <RequestReference>SONDERANGEBOT</RequestReference>
</OfferQueryRequest>

To fetch details, the client now uses the following request whose content is slightly incorrect:

The server then responds with:

If the server supported XML-POST(-S), the request could also have been realized via a POST of the following body:

Documentation [EN]

Document_type: Offer

Related pages