* We want to create a pickleball court reservation Python bot that uses curl_cffi to make rest calls and mimics a regular browser -- this bot will be hitting external APIs that we do not control, so we need to be smart about handling behavior anomalies.
* The bot needs to load a configuration file in json on startup which has the "BaseAPIUrl" as a configuration (which we'll set to "https://future.ourclublogin.com/api" ). We will also need to add the login username and password to the configuration -- note that in the configuration we will have a password like "Goliath00!!@", but when we use the value it becomes "Goliath00\041\041@" (notice the ascii escaping).
* Here is an example login query using cURL (we want the bot to mimic the headers):
*** We need to store the login query token and expiration in a file and use it for future requests. We should also store the time we generated the token in the file. We want to have the bot automatically login every time the token is 3 days old OR whenever we are past the tokenExpiration date.
* In the configuration file, we need a "Reservations" section that allows us to configure when the bot should be reservering. An example reservation configuration would be like: Day: Wednesday, Time: 19:00:00-08:00, Courts: [{Court: Court_1, Account: ToniB}, {Court: Court_2, Account: Lee}, {Court: Court_3, Account: Treve}, {Court: Court_4, Account: JoCampbell}, Reservation_Making_Behavior: Weekday_Reservation_Type]
** We also need a way to configure reservation accounts, an example reservation account configuration would be like: {Name: ToniB, Id: 6964}
** We also need a way to configure pickleball courts, an example pickleball court reservation would be like: {"Court": "Court_1", "Id":1, "Name":"Pickleball Court - 1","ResourceTypeId":2,"AssignedResourceId":130,"IsAssignedResourceSelectable":true}
** We also need a way to configure reservation making behavior types -- EG to reserve the court 7 days in advance, at 04:29:00-08:00 try twice with 10 second delay, at 4:30 try 10 times with 10 second delay, at 4:31 try 10 times with 10 second delay, at 4:35 try once (obviously make this in a configurable way).
--- obviously all of these types and examples need to reflect proper json formatting (and there should be validation on app startup to check if something is wrong)
* Here is an example API request for reserving a court that we want to support ("PrimaryCustomerId" is the field that needs to match the configured account ID.):
** Note that we do not want the bot to actually make court reservations yet, just build the code for doing it, but don't have it actually be triggered yet. Have a dummy print happen at the trigger time instead.
** When success happens for court reservation, the response looks like:
* I tried to book a court for 7 days in advance with a weekend reservation type, and it booked the court right away, instead of waiting for the specified booking times. The bot should only attempt to make the reservations in live mode at the time of the reservation.
* Instead of having to start the bot every day, update it to just run continuously. If it every crashes, the service will just auto-restart... No reason to require 7 cron jobs--1 for every day.
