YetiRides API Documentation

graph TB
    Client[Client Applications]
    API[YetiRides API]
    Auth[Authentication Service]
    DB[(Database)]
    reCAPTCHA[Google reCAPTCHA]
    Storage[File Storage]
    Email[Email Service]

    Client -->|HTTP/HTTPS| API
    API -->|Authenticate| Auth
    API -->|CRUD Operations| DB
    API -->|Bot Protection| reCAPTCHA
    API -->|File Operations| Storage
    API -->|Notifications| Email

    subgraph Backend Services
        API
        Auth
        DB
        Storage
        Email
    end
        

sequenceDiagram
    participant C as Customer
    participant A as API
    participant R as reCAPTCHA
    participant E as Email Service
    participant Admin as Admin

    C->>A: Submit Booking Request
    A->>R: Verify reCAPTCHA Token
    R-->>A: Validation Result
    
    alt Valid Token
        A->>A: Process Booking
        A->>E: Send Email to Admin
        A-->>C: Booking Confirmation
        E->>Admin: New Booking Notification
    else Invalid Token
        A-->>C: Error Response
    end
        

flowchart LR
    A[Start] --> B{Has Token?}
    B -->|Yes| C[Validate Token]
    B -->|No| D[Login Required]
    C -->|Valid| E[Access Granted]
    C -->|Invalid| D
    D --> F[Login]
    F --> G[Generate Token]
    G --> E
        

flowchart TD
    A[Admin] -->|Login| B[Dashboard]
    B -->|Manage Treks| C[Trek Management]
    B -->|Manage Blogs| D[Blog Management]
    B -->|View Bookings| E[Booking Management]
    
    C -->|Add Trek| C1[New Trek Form]
    C -->|Edit Trek| C2[Edit Trek Form]
    C -->|Delete Trek| C3[Confirm Delete]
    
    D -->|Add Blog| D1[New Blog Form]
    D -->|Edit Blog| D2[Edit Blog Form]
    D -->|Delete Blog| D3[Confirm Delete]
    
    E -->|New Bookings| E1[Process Bookings]
    E -->|Contact Enquiries| E2[Handle Enquiries]
        

erDiagram
    User ||--o{ Booking : makes
    User ||--o{ ContactUs : submits
    Trek ||--o{ Booking : receives
    Blog ||--|| User : created_by
    
    User {
        int id
        string name
        string email
        string role
        string address
        string phone
    }
    
    Trek {
        int id
        string data_type
        string title
        string location
        decimal price
        string duration
        string difficulty
        string type
        float distance_km
        text description
        string featured_image
        boolean is_featured
        boolean is_active
        json trek_days
    }
    
    Blog {
        int id
        string title
        text content
        string featured_image
        boolean is_active
        int user_id
    }
    
    Booking {
        int id
        string trek_name
        string name
        string email
        string country
        string phone
        int adults
        int children
        string subject
        text message
    }
                        

sequenceDiagram
    participant C as Client
    participant M as Middleware
    participant A as API Controller
    participant D as Database
    
    C->>M: HTTP Request
    M->>M: Validate Token
    M->>M: Check Permissions
    
    alt Invalid Auth
        M-->>C: 401/403 Error
    else Valid Auth
        M->>A: Forward Request
        A->>D: Query Data
        D-->>A: Return Data
        A-->>C: JSON Response
    end

    Note over C,D: All responses follow standard format