NextPax Supply API Updates – March 2026

Real-time notifications, smarter Airbnb pricing, and improved channel control

We’re excited to share the latest updates to the NextPax Supply API. This release focuses on real-time communication, better Airbnb reservation handling, and increased flexibility for channel management.

Below, we highlight the most important updates and what they mean for your integration.

🚀 Introducing the Notifications API (NAPI)

One of the biggest upgrades in this release is the launch of the NextPax Notifications API (NAPI) — a production-ready webhook service designed to deliver real-time updates to your systems.

Why this matters

Until now, integrations relied heavily on polling. With NAPI, you can now react instantly to events, improving both performance and user experience.

Key capabilities

• Real-time event delivery for:
  • Bookings
  • Messages
• FIFO delivery to preserve event order
• Flexible authentication:
  • Existing credentials
  • Basic Auth or X-API-Token
• Secure webhook validation during setup
• Configurable subscriptions per event type
• Smart retry logic:
  • Automatic retries
  • Temporary deactivation of failing endpoints
  • Automatic reactivation

👉 Important: Your system must return a 200 OK response to confirm successful processing and stop retries.

Best practice: Hybrid approach

Even with webhooks, we strongly recommend maintaining polling as a fallback:

• Bookings API → GET /bookings every 10–30 minutes
• Messaging API → GET /threads & GET /messages every 10–30 minutes

Use modifiedSince to efficiently retrieve incremental updates.

💡 This hybrid setup ensures maximum reliability, even if a webhook is delayed or temporarily fails.

🏡 Airbnb: Improved Price Recalculation for Reservation Changes

We’ve introduced a new Airbnb channel setting to solve a long-standing challenge with reservation modifications, also known as alterations.

The problem

When availability was closed after a booking, it also impacted LOS (Length of Stay) records — preventing Airbnb from recalculating prices correctly when guests changed their stay.

The solution

New setting:
exclude_availability_data_from_los_records

What it does

• Sends only pricing data to Airbnb LOS records
• Keeps availability management via the calendar endpoint
• Enables accurate price recalculation during reservation changes

Important considerations

To use this correctly:

• ✅ Always send pricing — even for booked dates
• ⚠️ Arrival/departure restrictions will be ignored in LOS records
• 👉 Use LOS rates (instead of periodic rates) to maintain restrictions

💡 Result: A smoother guest experience and fewer pricing inconsistencies.

⚙️ Channel Management Enhancements

Take Over Existing Listings

You can now take control of existing listings on channels instead of creating new ones.

Supported channels:

• Booking.com
• Airbnb

Use cases

• Migrating from another PMS or channel manager
• Avoiding duplicate listings
• Maintaining existing reviews and ranking

Key requirement

You must provide the correct identifiers depending on the property type (e.g. channelPropertyId, channelRoomId).

Airbnb Host ID Support

You can now define a property-level Airbnb Host ID:

• Useful when properties belong to different Airbnb accounts
• Cannot be overwritten once set
• Empty values are rejected

💡 This gives more flexibility for multi-account property managers.

⚙️ Channel Settings Updates

Airbnb: Minimum Notice Before Booking

New setting:
minimum_notice_before_booking

• Defines required hours before a booking can be made
• Overrides account-level settings
• Works on:
  • Property level
  • Property manager level
• Values are exported as-is (no check-in time adjustments)

Booking.com: Payments by Booking.com

We’ve clarified the behavior of:
payments_by_booking_enabled

👉 When enabled:
All related payment settings become mandatory, including:

• Payout method
• Payment frequency

🔄 Backward Compatibility Improvements

To make integrations more robust:

Property Reviews API

We now support both naming conventions for date fields:

• createdAt and created_at
• arrivalDate and arrival_date
• departureDate and departure_date

💡 This ensures smoother transitions for legacy integrations.

💡 What This Means for You

This release is all about reliability, flexibility, and better channel alignment:

• ⚡ Real-time operations with Notifications API
• 🏡 Better Airbnb booking modification flows
• 🔗 Easier migrations and channel control
• 🧩 More flexible and resilient integrations

👉 What to Do Next

1. Implement the Notifications API (NAPI) for real-time updates
2. Keep your polling fallback in place
3. Review Airbnb settings if you support reservation changes
4. Evaluate take-over functionality if migrating properties

If you have questions or want to explore how these updates fit your setup, reach out to the NextPax team or visit the developer portal.