harbor-bot

Pickleball court reservation bot for Harbor Isles Tennis & Fitness Club.

Setup

1. Install dependencies:

   pip install -r requirements.txt
   

2. Configure config.json with your settings (see Configuration section below).

Usage

# Show configuration and next trigger times
python harbor_bot.py --show-config

# Test login
python harbor_bot.py --test-login

# Run as daemon (recommended - runs continuously)
python harbor_bot.py --daemon

# Run daemon in live mode (actually makes reservations at scheduled times)
python harbor_bot.py --daemon --live

# Run once and check for reservations (one-shot mode)
python harbor_bot.py --run

# Test booking a specific court (dry run)
python harbor_bot.py --test-book Court_1 Saleh 2026-01-19 "19:00:00-08:00"

# Test booking a specific court (live - actually books!)
python harbor_bot.py --test-book Court_1 Saleh 2026-01-19 "19:00:00-08:00" --live

Daemon Mode

The recommended way to run the bot is in daemon mode (--daemon). It will:

1. Run continuously, checking for reservations every minute
2. Wait for the exact scheduled times in the ReservationBehavior before attempting
3. Automatically refresh authentication when needed
4. Track successful reservations to avoid duplicates

To run in production with auto-restart on crash, use a process manager like systemd:

# /etc/systemd/system/harbor-bot.service
[Unit]
Description=Harbor Bot Pickleball Reservation Service
After=network.target

[Service]
Type=simple
User=your-user
WorkingDirectory=/path/to/harbor-bot
ExecStart=/usr/bin/python3 harbor_bot.py --daemon --live
Restart=always
RestartSec=10

[Install]
WantedBy=multi-user.target

Then enable and start:

sudo systemctl enable harbor-bot
sudo systemctl start harbor-bot
sudo journalctl -u harbor-bot -f  # View logs

Configuration

The config.json file contains:

API Settings

• BaseAPIUrl: API endpoint URL
• CompanyId: Club company ID
• ClubId: Club ID
• AppointmentItemId: Item ID for pickleball reservations

Login

• Username: Your login username
• Password: Your password (stored as-is, e.g., "Goliath00!!@")

Accounts

List of accounts that can be used for reservations:

{"Name": "ToniB", "Id": 6964}

Courts

List of available courts:

{
  "Court": "Court_1",
  "Id": 1,
  "Name": "Pickleball Court - 1",
  "ResourceTypeId": 2,
  "AssignedResourceId": 130,
  "IsAssignedResourceSelectable": true
}

Reservation Behaviors

Defines how reservations are attempted. Important: Times must be in ascending order.

{
  "Name": "Weekday_Reservation_Type",
  "DaysInAdvance": 7,
  "AttemptSchedule": [
    {"Time": "04:29:00-08:00", "Attempts": 2, "DelaySeconds": 10},
    {"Time": "04:30:00-08:00", "Attempts": 10, "DelaySeconds": 10},
    {"Time": "04:35:00-08:00", "Attempts": 1, "DelaySeconds": 0}
  ]
}

• DaysInAdvance: How many days before the reservation date to attempt booking
• AttemptSchedule: List of attempt windows (must be in chronological order)
  • Time: When to start attempting (in timezone format like "04:30:00-08:00")
  • Attempts: Number of booking attempts in this window
  • DelaySeconds: Delay between attempts

Reservations

Scheduled reservation configurations:

{
  "Day": "Wednesday",
  "Time": "19:00:00-08:00",
  "ReservationBehavior": "Weekday_Reservation_Type",
  "Courts": [
    {"Court": "Court_1", "Account": "Saleh"},
    {"Court": "Court_2", "Account": "ToniB"}
  ]
}

Files

• config.json - Main configuration
• token_data.json - Stored authentication token (auto-generated)
• reservation_success.json - Tracks successful reservations (auto-generated)

Token Management

• Tokens are automatically saved and reused
• Token refresh occurs when:
  • Token is expired
  • Token is older than 3 days