Closed dineshraj closed 8 years ago
Likely not since the urls in urls.json inside /src points to the US urls rather than UK urls.
This should be easily fixable by replacing the urls with the corresponding urls from the UK version, this is given that they have the same endpoints exposed (which in some non-US versions is not true).
Yea, I saw that upon further exploration of the app. Thanks!
I wonder if the API is the same though?
If so we could add it in pretty easily.
It seems to be different. The store finder URL is https://www.dominos.co.uk/storefindermap/storesearch?SearchText=${post code}
Getting the menu:
https://www.dominos.co.uk/ProductCatalog/GetStoreCatalog?collectionOnly=false&menuVersion=636119029800000000&storeId=${store id}
It wants a menu version. I left the example I got.
Getting store context:
https://www.dominos.co.uk/ProductCatalog/GetStoreContext?_=1476466590187
This returns the menu version and store id but requires some sort of id. This ID is in the session on the browser for the dominos site. They use optimizely.com for tracking which sets the ID. This is as far as I got. I feel it's too difficult to setup for the UK store.
Sweet info.
I'm from the UK and currently writing a node app for handling / simplifying group orders - would this API work for our stores ?
If it helps, the menu for a store seems to be returned from a call like this:
https://www.dominos.co.uk/Tracking/ListingProductsDisplayed?productIds=1500%7C15%7C18%7C17%7C24%7C1046%7C55%7C13%7C1052%7C14%7C1358%7C56%7C39%7C1474%7C23%7C34%7C59
It seems to use a cookie to determine your location for the menu though