search

Alkaar / resy-booking-bot

🔫 Helps to snipe hard to get reservations at restaurants that use resy
411 stars 215 forks source link

Required headers for /user lookup #12

Closed ZachWhitford closed 2 years ago

ZachWhitford commented 3 years ago

Which headers did you find were required for the /user endpoint lookup? Getting a 419 back from the endpoint while it seems I'm using all the same ones as you. Any pointers?

ZachWhitford commented 3 years ago

Just to clarify as well, the exact same request works on non /user endpoints so there must have been a backend change but would love your opinion

Alkaar commented 2 years ago

Sorry for not keeping up to date on these issues as I've not used nor maintained the bot due to the pandemic. As of now, it seems that Resy updated the API endpoint so the contract is completely different. I have tried to go through the bot to fix things but I haven't gotten around to fixing it completely. Just wanted to make you all aware.

ZachWhitford commented 2 years ago

I have figured out a bypass and the new endpoint.

On Tue, Mar 8, 2022 at 9:43 PM Alkaar @.***> wrote:

Sorry for not keeping up to date on these issues as I've not used nor maintained the bot due to the pandemic. As of now, it seems that Resy updated the API endpoint so the contract is completely different. I have tried to go through the bot to fix things but I haven't gotten around to fixing it completely. Just wanted to make you all aware.

— Reply to this email directly, view it on GitHub https://github.com/Alkaar/resy-booking-bot/issues/12#issuecomment-1062499236, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB4UB7A2Y36X3H47KEJFUADU7AF6JANCNFSM5BDLEYWA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

Alkaar commented 2 years ago

Glad you figured it out. FYI I updated the bot to work with the new Resy API along with a few minor fixes. LMK your thoughts on it.

Regarding the endpoints, the /user endpoint is not used in the code. I left it in there anyway because I originally was using it to write the bot and then realized later on I didn't need it. Felt it didn't hurt to leave it there as a reference.

Alkaar commented 2 years ago

Just to update this thread, I decided to remove the /user endpoint completely to avoid confusion. If there's a use case for it, I can always bring it back.