GetProfile
The request
https://b2b.beispielserver.com/?BuyersID=B127645&Password=secret&RequestName=GetProfileRequest&version=1.3
receives the following response:
<?xml version="1.0" encoding="utf-8" ?>
<GetProfileResponse xmlns="urn:veloconnect:profile-1.3" xmlns:vct="urn:veloconnect:transaction-1.0">
<vct:BuyersID>B127645</vct:BuyersID>
<vct:ResponseCode>200</vct:ResponseCode>
<VeloconnectProfile>
<Implements>
<Operation>GetStatus</Operation>
<Binding>URL-S</Binding>
</Implements>
<Implements>
<Operation>Rollback</Operation>
<Binding>URL-S</Binding>
</Implements>
<Implements>
<Operation>GetItemDetails</Operation>
<Binding>URL-S</Binding>
</Implements>
<Implements>
<Operation>GetItemDetails</Operation>
<Binding>XML-POST-S</Binding>
</Implements>
<Implements>
<Operation>GetItemDetailsList</Operation>
<Binding>XML-POST-S</Binding>
</Implements>
<Implements>
<Operation>GetItemDetailsList</Operation>
<Binding>URL-S</Binding>
</Implements>
<Implements>
<Transaction>Order</Transaction>
<Binding>URL-S</Binding>
</Implements>
<Implements>
<Transaction>Order</Transaction>
<Binding>XML-POST-S</Binding>
</Implements>
<Implements>
<Transaction>OrderInOnlineShop</Transaction>
<Binding>XML-POST-S</Binding>
<URI>https://shop.beispielserver.com/vc_order.jsp</URI>
</Implements>
<Implements>
<Transaction>TextSearch</Transaction>
<Binding>URL-S</Binding>
</Implements>
<Implements>
<Transaction>TextSearch</Transaction>
<Binding>XML-POST-S</Binding>
</Implements>
<Implements>
<Operation>OfferQuery</Operation>
<Binding>URL-S</Binding>
</Implements>
<Implements>
<Operation>OfferDetails</Operation>
<Binding>URL-S</Binding>
</Implements>
<Implements>
<Operation>OrderConfirmationQuery</Operation>
<Binding>URL-S</Binding>
</Implements>
<Implements>
<Operation>OrderConfirmationDetails</Operation>
<Binding>URL-S</Binding>
</Implements>
<Implements>
<Operation>DeliveryNoteQuery</Operation>
<Binding>URL-S</Binding>
</Implements>
<Implements>
<Operation>DeliveryNoteDetails</Operation>
<Binding>URL-S</Binding>
</Implements>
<Implements>
<Operation>InvoiceInformationQuery</Operation>
<Binding>URL-S</Binding>
</Implements>
<Implements>
<Operation>InvoiceInformationDetails</Operation>
<Binding>URL-S</Binding>
</Implements>
<Property>
<Key>OrderInOnlineShop.TransactionID</Key>
<Value>online-basket</Value>
</Property>
<Property>
<Key>Order.Availability</Key>
<Value>true</Value>
</Property>
<Property>
<Key>Order.DeliveryDate</Key>
<Value>line</Value>
</Property>
<Property>
<Key>Order.Backlog</Key>
<Value>line</Value>
</Property>
<Property>
<Key>Order.BacklogDefault</Key>
<Value>false</Value>
</Property>
<Property>
<Key>quantityUnitCode.EA</Key>
<Value>false</Value>
</Property>
<Property>
<Key>RecommendedRetailPrice.Netto</Key>
<Value>false</Value>
</Property>
<UnsupportedQuery>Invoice-OrderID</UnsupportedQuery>
<UnsupportedQuery>Invoice-OrderConfirmationID</UnsupportedQuery>
<SpecialRequestReference>
<RequestReference>SONDERANGEBOTE</RequestReference>
<Description>Aktuell wechselnde Sonderangebote</Description>
</SpecialRequestReference>
<SpecialRequestReference>
<RequestReference>NEW</RequestReference>
<Description>Neue Artikel im Sortiment</Description>
</SpecialRequestReference>
</VeloconnectProfile>
</GetProfileResponse>
First of all, the following special feature is evident: The OrderInOnlineShop transaction is not addressed via the default URL, but a different one.Â
Support for transactions and operations is provided in the URL-S as well as the XML-POST-S bindings in some cases, and only in the URL-S binding in other cases such as those involving all document management operations.
Furthermore, the Veloconnect 1.3 server here supports all new document management operations, although no direct referencing of order invoices or order confirmations is possible (UnsupportedQuery).
For the OfferQuery operation, the server provides two special references here:
SPECIAL OFFERS for ongoing, changing special offers
NEW for new articles in the assortment