R

Developers

API overview

Channel partners authenticate with HMAC headers X-Rega-Channel-Id, X-Rega-Timestamp, and X-Rega-Signature. In development, signature checks are lenient.

Public endpoints

  • GET
    /api/channels/v1/products

    Full inventory feed — hotels, flights, buses, lounges, transfers, eSIM, bundles (Booking.com / Expedia format).

  • GET
    /api/channels/v1/availability?type=&city=&date=

    Dated availability for hotels, flights, and buses.

  • POST
    /api/channels/v1/reservations

    Create reservation — accepts channel-native JSON (Booking.com or Expedia shape).

  • GET
    /api/channels/v1/reservations/{ref}

    Reservation status lookup for OTA partners.

  • POST
    /api/channels/v1/reservations/{ref}/cancel

    Cancel an OTA-originated booking.

  • POST
    /api/promo/validate

    Validate a promo code before checkout.

  • GET
    /api/bus/search?from=&to=&date=&corridor=

    Search bus trips across corridors.

OTA sandbox

Try channel inventory and reservation endpoints in the browser (development signatures).

Open sandbox

Partner portal

Bus operators use POST /api/partner/auth with their company API key, then GET /api/partner/dashboard for trips and bookings.

Open partner login

Full specification is in docs/api.md in the repository.