If we search a product in search by category name. the response leads us the message_id which we can use to call the onSearch api. The problem here is that we call the onSearch api 5 times which i am not aware that is hardcoded or not but still all the apis are pointing to the same request_url and the request_body is also identical for all the onSearch apis.
The problem here is we get the whole response in the second api response as well and all the other apis after that have the same response. If all the apis are having same response than why it is called 5 times.
The detailed view of the issue can be seen in the screenshots attached.
As you can see that in the first all the search api the request urls are same which are
https://qa.box.beckn.org/api/beckn/onSearch
and the request payload is
Array<{message_id: "486b9fd3-ddad-4bb5-b9d2-0b8ca0908e1a"}>
and in the second and third response of the on_search api the response are same. I have highlighted the ids for better understanding.
If we search a product in search by category name. the response leads us the
message_idwhich we can use to call theonSearchapi. The problem here is that we call theonSearchapi 5 times which i am not aware that is hardcoded or not but still all the apis are pointing to the samerequest_urland therequest_bodyis also identical for all theonSearchapis.The problem here is we get the whole response in the second api response as well and all the other apis after that have the same response. If all the apis are having same response than why it is called 5 times.
The detailed view of the issue can be seen in the screenshots attached.
As you can see that in the first all the search api the request urls are same which are
https://qa.box.beckn.org/api/beckn/onSearchand the request payload isArray<{message_id: "486b9fd3-ddad-4bb5-b9d2-0b8ca0908e1a"}>and in the second and third response of the
on_searchapi the response are same. I have highlighted the ids for better understanding.