-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not fetching full history #7
Comments
I'll look into this coming weekend probably. Thanks for reporting. If you'd like to poke around the codebase, feel free to. |
So, looks like Swiggy has started to limit the full history from the API, the total number of orders are now capped to Since the data from the API (and the web) itself isn't available I don't think there's much we can do about it. I can probably write a weekly exporter which runs as a cron job to fetch week orders and store the data but the object in it's current form won't have much use. A bit disappointed but I guess we have to live with it. Thanks for using this project, I'll try to write the exporter soon 😄 |
for me, it's only giving 344, with the message to use the App for full history. @mr-karan possible to extract apis from the app? |
the limit is in last 1 year and not any arbitrary number |
what you can possibly do is look into the internal api for swiggy app. using something like mitmproxy and get it to fetch older orders ? possible ? the app uses certificate pinning so you have to patch the apk with apk-mitm in meantime |
I've been using swiggy for more than a year, but the tool only picked the last 35 or so orders whereas the total order count should've been well above 200.
Maybe the API now returns paginated data?
The text was updated successfully, but these errors were encountered: