The last-mile problem in pricing
A better price does nothing while it sits in a dashboard. Many teams copy prices into a PMS, channel manager or ticketing platform by hand, which is slow and error-prone.
- Updated prices never reach the booking channels
- Manual copying introduces errors and delay
- Native PMS and channel-manager integrations take months to build
- Different systems expect different formats
- No record of what was sent, when and where
How Luska distributes prices
A webhook any system with an API can receive, plus a log of every dispatch.
Webhook delivery
Send changed rates to your PMS, channel manager or your own endpoint as JSON. Any system that can receive an HTTP request can use it.
Shared secret
Each request carries a secret you set, so your endpoint can reject requests that did not come from Luska.
Sent after autopilot applies changes
When autopilot applies price changes, the new rates are dispatched straight away. You can also push the latest changes manually at any time.
Dispatch log
Every dispatch is logged with its time, HTTP status, duration and number of rates sent, so failures are visible.
CSV and email digest (in development)
Delivery of rates as a CSV attachment or a daily email digest is being built and is not yet available.
Key Benefits
Frequently Asked Questions
Which PMS or channel managers does this work with?
Any system that can receive a webhook, directly or through middleware. There are no native connectors for specific PMS or channel managers yet.
How are webhooks secured?
Each request includes a shared secret that you set, in a request header. Your endpoint should check it and reject requests without it.
Can I review changes before they're pushed?
Yes. Only changes that autopilot applies automatically are dispatched straight away. Changes above your auto-apply threshold wait in the approval queue. After approving them, use the manual push to send them.
What happens if a dispatch fails?
The failure is recorded in the dispatch log with its status code and response, and the price decision in Luska is unaffected. Failed dispatches are not retried automatically; push again once the endpoint is fixed.