-
Notifications
You must be signed in to change notification settings - Fork 10
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
[FEATURE]: OpenTable API #7
Comments
Quick update: So I've figured out that sending the following HTTP Request message will email the user for confirmation, i've marked where to put the email with the
It appears the header The server will respond with a message with the following body:
The |
After the request in the above is sent, two further requests must be made. First, a request must be made of content type
|
Just looked into the above, and it appears one does not even need to login to make a reservation on open table, so while the above info is useful, we do not need it. |
It appears the sha256Hash field values are analagous to API Keys, but they work depending on the requested function. So logging in has its own sha256Hash key, searching has its own key, and reserving has its own key |
Working on the search function right now, and managed to get through to the opentable servers on go. Please note, there's some funky behavior with how the opentable servers handle the |
Quick Note:
This will trigger a response from the server with the following example body:
Each entry in the |
Closed with recent PR |
Is there an existing issue for this feature?
Description of the problem
If a restaurant is only available for reservation on opentable, the app does not work
Planned Solution
Create an Open Table implementation of the API interface
Alternatives
I've thought of creating a new object / application for Open Table specifically since it uses 2-step login, but I believe generalizing the bot's API pkg to represent 2-step login is a good idea.
Solution Specifics
I've already begun dissecting the internals of Open Table's API using postman, still unsure of how to manage logins, but I believe I might be able to introduce semantics for token refreshing so that multiple logins may not be required. This can improve the response times on the resy API as well
The text was updated successfully, but these errors were encountered: