Rider Status Change Webhook

This webhook event occurs when there is an information of rider details for an order is found.


Written By Ops UrbanPiper (Collaborator)

Updated at March 27th, 2020

Rider Status Update API - https://api-ordering-docs.urbanpiper.com/?shell#rider-status-change

  1. How does the Rider Status Update works?
    - From the time the order is placed and it is delivered to the end customer, whereabouts information of the delivery rider is being captured from the aggregator and send it to the POS system.

  2. What is the type of HTTP request?
    - POST

  3. Can I get the POS store id in the request payload?
    - Yes

  4. From which all aggregators I can expect the Rider details information?
    - Zomato, Swiggy

  5. Is it mandatory to capture the data?
    - It's additional information for the merchant to track the delivery rider.

  6. Does the Rider Status information will be available for all the orders of Zomato and Swiggy?
    - Yes, but again if the aggregators are sending the information, we do relay it to POS.

  7. What is the OTP to be shared with Rider?
    - The last 4 digits of the customer's phone number. This OTP is required only for Zomato orders.

  8. Do I need to maintain all the status under status_updates array?
    - Yes. You need to show all the status updates to keep a track of the rider.

  9. What all parameters are mainly important to show to the merchant?
    - Delivery Rider phone number, name, current_state.

  10. Under store.ref_id, is this the POS store code?
    - Yes.

  11. Can you send the Rider Status Information if the merchant is on the Hybrid module on Zomato and when delivery_type of the order is self-delivery?
    - No.

Was this article helpful?