Integration Hub: Order Webhook Settings

Integration Hub: Order Webhook Settings





A webhook is a service that allows a program to send data to another the moment a particular event occurs.


Configuration in Integration Hub

Navigation: Log into Back Office, then select Home > Integration Hub

A screenshot of a website AI-generated content may be incorrect.

 

  1. On the Integration Hub page: click Order webhook. The Webhooks page appears.


  2. Request Header – Contains fields for API Key and Value. They both will be provided by the partner and are a form of authorization key, so that when webhook is sent with the key value they trust that webhook and allow it.



  3. Close Order Web Hooks – The Close webhook is triggered when a check is closed, and information about the closed check is sent. If someone wants to receive data from our system, then they need to enter the URL into the field and enable the Close Order Web Hooks toggle. If this toggle is Disabled (set to NO), then they won’t receive any data, even if there’s a URL in the field.



  4. Open Order Web Hooks – An Open webhook is triggered when customer has placed an order on OLO. The textbox is to enter the URL. We will send the check information to the webhook where the checks are created from OLO and, if Enabled (set to YES), the check information is sent to the third party (webhook). This check information will be in JSON form. When Disabled (set to NO), we will not be sending any Check information to webhooks.


  5. Update Order Web Hooks – Triggered when there is any change on a check -such as adding an item or changing the table. If Enabled (YES), any update to the check information then the same will be updated to webhook. If Disabled (NO), no updates will be reflected in webhook.


  6. 3rd Order Web Hooks is Active – If Enabled (set to YES), data will be sent via the URL which is inserted into the Open Order Webhooks. This is triggered when an order is placed in POS and a request header for authorization purposes. If a partner specified any key, the data is sent via API key so that they can trust the source. If Disabled (set to NO), then no action takes place.

    • Related Articles

    • Enable PUC Integration

      PUC Integration workflow: Step 1: Placing an order.   Customer can login to the online order app/website and places an order via OLO. Step 2:  Receiving the order.  Once the order is received by the POS a pick-up code need to be generated. Step 3: ...

    • Back Office: Integration Hub User Manual

      Description: The steps to subscribe to and use the Integration Hub add-on Navigation: Log into your Store, then select Upgrade > Manage Plan > Enterprise Level At the Enterprise level, purchase the amount of Integration Hub add-ons based on the ...

    • OLO Order Throttling

      Making Settings: Throttling settings need to be done under Zenpepper Admin. For this, you should login to Back Office and click ‘Web Order’ on the left menu, follow the path Stores -> Change Settings -> Throttling Settings. Order throttling can be ...

    • ValuTec Integration

      Implementation in the Back Office:               Page Navigation: My Stores >> Settings >> Payment         A new option “Valutec” should be displayed when the payment type SPPax is chosen.           By default, this option will be in disable mode. ...

    • Enabling Order Types

      Enabling Order Types: Select “Operation” Select “POS Settings” You will be able to enable/disable the order types After completed, scroll up and select “Save Changes” Changes have now been updated