Warden API
    Warden External API
    • Warden External API
    • Auth
      • Credential Refresh
        GET
    • Booking Engine
      • Get Property Listings
        GET
      • Get Bed Availability
        POST
      • Get Room Type Listings
        GET
      • Get Plan Options for Channel and Room Types
        POST
      • Generate Plan for Channel and Room Types
        POST
      • Create Booking
        PUT
    • API
      • Get Company Details
        GET
      • Get Channels
        GET
      • Get Bookings
        GET
      • Get Residents
        GET
      • Get Payments
        GET
      • Get Transactions
        GET

    Auth

    All API requests to Warden are secured using an OAuth 2.0 strategy. Before calling any endpoint, you must obtain an Access Token using your credentials.

    How It Works#

    1.
    Use your Warden-Id and Warden-Secret to call the Credential Refresh endpoint
    2.
    The response returns an accessToken valid for 15 minutes
    3.
    Pass this token as a Bearer Token in the Authorization header on every subsequent API request
    4.
    When the token expires, call Credential Refresh again to get a new one

    Keeping Your Credentials Safe#

    Your Warden-Id and Warden-Secret are sensitive and should be treated like a password. Follow these practices:
    Never expose them in client-side code or public repositories
    Only use them to call the Credential Refresh endpoint — they are not valid for any other API call
    Store them securely using environment variables or a secrets manager
    Modified at 2026-05-03 12:42:12
    Next
    Credential Refresh
    Built with