Integration
The following operations are supported. For a formal definition, please review the Service Description.
-
GetAllMessages
Gets all unreaded messages in XML format. -
GetAllMessagesV2
Gets all unreaded messages in XML format. -
GetAllMessagesV3
Gets all unreaded messages in XML format. -
GetMenu
Gets the restaurant menu. The result objects includes products and options. -
GetMenuLegacy
Gets the restaurant menu. The result objects includes products and options. -
GetMenuPandora
Gets the restaurant menu. The result objects includes products and options. -
GetMenuTest
Gets the restaurant menu. The result objects includes products and options. -
GetMessage
Gets top one unreaded messages in XML format. -
GetMessageV2
Gets top one unreaded messages in XML format. -
GetPaymentTypes
Gets the all avaliable payment types. -
GetRejectReasons
Returns available reject reasons -
GetRestaurantDeliveryAreas
Gets the all delivery areas of restaurant -
GetRestaurantList
Gets all related restaurants list. - GetRestaurantOrderMessagesTest
-
GetRestaurantPointsAndComments
Gets the restaurant points and comments. -
GetRestaurantPromotions
Gets the restaurant promotions. -
GetRestaurantStatus
Restaurant Status -
GetRestaurantStatusV2
Restaurant Status -
GetTopMessages
Gets top unreaded messages in XML format. -
GetTopMessagesV2
Gets top unreaded messages in XML format. -
GetWaitingApprovalOrderReport
Gets tabgida waiting orders in XML format. - Healthcheck
-
IsRestaurantOpen
Returns whether a restaurant open or not. -
MessageSuccessful
Set message received successfully. -
MessageSuccessfulV2
Set message received successfully -
SetRestaurantForOrder
Redirects order another restaurant of the account. -
SetRestaurantServiceTime
Sets restaurant service time. -
UpdateOrder
Updates order state. -
UpdateOrderV2
Update order state with rejectReasonId. -
UpdateRestaurantDeliveryAreaState
Updates restaurant delivery area state. -
UpdateRestaurantState
Updates restaurant state. -
UpdateValeOrder
Updates vale order state. -
UpdateValeOrderV2
Updates vale order state.
This web service is using http://tempuri.org/ as its default namespace.
Recommendation: Change the default namespace before the XML Web service is made public.
Each XML Web service needs a unique namespace in order for client applications to distinguish it from other services on the Web. http://tempuri.org/ is available for XML Web services that are under development, but published XML Web services should use a more permanent namespace.
Your XML Web service should be identified by a namespace that you control. For example, you can use your company's Internet domain name as part of the namespace. Although many XML Web service namespaces look like URLs, they need not point to actual resources on the Web. (XML Web service namespaces are URIs.)
For XML Web services creating using ASP.NET, the default namespace can be changed using the WebService attribute's Namespace property. The WebService attribute is an attribute applied to the class that contains the XML Web service methods. Below is a code example that sets the namespace to "http://microsoft.com/webservices/":
C#
[WebService(Namespace="http://microsoft.com/webservices/")] public class MyWebService { // implementation }
Visual Basic
<WebService(Namespace:="http://microsoft.com/webservices/")> Public Class MyWebService ' implementation End Class
C++
[WebService(Namespace="http://microsoft.com/webservices/")] public ref class MyWebService { // implementation };
For more details on XML namespaces, see the W3C recommendation on Namespaces in XML.
For more details on WSDL, see the WSDL Specification.
For more details on URIs, see RFC 2396.