Skip to content

Changelog

Release notes for the Himalayan Guardian developer documentation portal.

1.1.0 — 22 September 2026

Added

  • Quote v2 — POST /api/external/v2/reference/quote prices a trip from the traveller's date of birth (dobs) and durationDays. The age is taken on the last day of the policy, reported as agesUsed; endDate is the last insured day.
  • deviceSelectionPricing.devicePriceImpact on quotes: how much the total drops if the bundled device is excluded.
  • Orders are rejected when the traveller's age on the last covered day is outside the package's age range.

Deprecated

  • POST /api/external/v1/reference/quote (quote from ages). Stops working after 31 December 2026. Responses carry Deprecation, Sunset and Link headers. See Migrating from v1.

Changed

  • Travellers: medicalHistory is now required for partners.
  • Orders: policy issuance mode, document format limits, agency-field rules and rejection causes documented as enforced.
  • Authentication: /auth/token failures are 400, not 401; rotating a secret does not revoke issued tokens; credential expiry.
  • Rate limits documented (300/min and 5,000/hour per credential by default) with the 429 response and headers.
  • Payments: idempotency-key reuse rules, full status enums, status on the return redirect, paymentRef format, 403/409 causes.
  • Promo codes: response fields, which rejections share Invalid promo code, preview works on any order, partial group apply.
  • Errors: 429 and other statuses, details variants, which 409s to retry.

1.0.0 — 28 August 2026

First release. Initial publication of the developer documentation portal at docs.himalayanguardian.com, covering all three Himalayan Guardian Nepal integration methods.

Added

Referral Links — no-code integration

  • Full setup guide for sales agencies and sales agents
  • Finding your Public Booking Link in the dashboard
  • Logo download and the anchor-tag snippet
  • Platform instructions for HTML, WordPress, Wix, Squarespace, email, social, and print/QR
  • Testing steps and a troubleshooting table

Booking Widget — embedded integration

  • Overview of the full-page iframe model, with browser support and customisation options
  • Integration guide: prerequisites, five-minute quickstart, five-step procedure, Content Security Policy, local testing, and an AI-assistant prompt
  • Payment verification guide with server-side examples for Node.js, Next.js, PHP, and Python
  • WordPress guide covering page templates, builder canvas templates, and platform-specific issues
  • Troubleshooting and support process

Partner API — full server-to-server integration

  • Overview with the booking flow, response envelope, and conventions for dates, identifiers, and pagination
  • Authentication, including token caching and lifecycle handling
  • Availability and quoting, covering quotes, the package catalogue, and routes
  • Booking, covering documents, travellers, and orders
  • Payments, covering hosted payment initiation, status verification, and idempotency
  • Promo codes, covering preview, apply, and remove for single orders and batches
  • Errors, documenting all three error shapes with a normalising parser
  • Examples, with a full cURL walkthrough plus complete Node.js and Python clients

Portal

  • Product-based structure, ready for additional Himalayan Guardian products
  • Side-by-side comparison of the three integration approaches
  • Himalayan Guardian branding, colours, and logo
  • Full-text search across all documentation

Product changelogs

Individual products track their own versions:

Product Changelog
Booking Widget Booking Widget changelog
Partner API API changelog