UrbanPiper Integrations

This document helps to do the UrbanPiper Integration at DineSuite of Applications. UrbanPiper is integrated with DinePlan (with DineConnect) and Only DinePlan. 

The document is divided into the following things 

  1. Urban Piper 
  2. Gateway 
  3. Common Steps in DinePlan
  4. DinePlan Integration (Applicable only if we do not use DineConnect).
  5. DineConnect Settings
UrbanPiper 

Decide on the Location Name and Location Code for the Customer. This is very important to take the customer to accept the Orders from Urban Piper.

  1. Request a Credentials (API Key, User, URL for a Customer) from UrbanPiper Team
  2. If we use only DinePlan for the integration, We have to create the Location Manually in Quint Dashboard
  3. The Webhook should be configured in Quint Dashboard as below 

 

image-1610018555991.png

The URL are 

Order placed https://dcgateway.azurewebsites.net/UrbanPiper/PushOrder
Order status update https://dcgateway.azurewebsites.net/UrbanPiper/PushOrderStatus
Order delivery status https://dcgateway.azurewebsites.net/UrbanPiper/PushRiderStatus
Stores create/update https://dcgateway.azurewebsites.net/UrbanPiper/StoreUpdate
Stores status change https://dcgateway.azurewebsites.net/UrbanPiper/StoreStatusUpdate
Catalogue publish through API https://dcgateway.azurewebsites.net/UrbanPiper/CatalogueUpdate
Item Stock In/Out https://dcgateway.azurewebsites.net/UrbanPiper/ItemUpdate
Gateway

Request Credentials for the Gateway from DinePlan Team. By giving the API Key, User, and URL from the UrbanPiper team. You need to get the Location Id and Location Code from the Gateway.

Steps in DinePlan

Here are the steps to be done at the DinePlan

STEP 1: Program Settings to be updated

PG.png

Menu Screen Menu name (used only if the DinePlan is used for UrbanPiper)
Price Tag

Price Tag name (used only if the DinePlan is used for UrbanPiper)

Location

Location Id from Gateway

Platform

Platforms that we are supporting (used only if the DinePlan is used for UrbanPiper)

Name

This is the Cloudinary URL. Request from the team for the Customer. (used only if the DinePlan is used for UrbanPiper)

https://cloudinary.com/

Key

This is the Cloudinary Key. Request from the team for the Customer. (used only if the DinePlan is used for UrbanPiper)

https://cloudinary.com/

Secret

This is the Cloudinary Secret. Request from the team for the Customer. (used only if the DinePlan is used for UrbanPiper)

https://cloudinary.com/

STEP 2: Configure the Screen as below

1. Create the Department With the Delivery for UrbanPiper in DinePlan and add the tags as below in the Ticket Listener

and It creates the Button below to filter tickets