Customizations
Customizations are the pricing rules that shape your recommended prices — seasonality, last minute prices, far out premium, day of week adjustments, demand factor, and custom seasonal profiles. They can be set on a single listing, on a group, or across a whole PMS account.
get_customizations
Shows the customizations currently set on one listing, group, or account. By default only the ones that are switched on are returned; ask for the switched-off ones too and you also get their saved settings. You can narrow the response to specific customizations rather than pulling all six.
Alongside the stored values you also get each customization described the way the dashboard shows it. That answers what the raw numbers cannot: what a market-driven type currently works out to as a percentage, whether an adjustment is a discount or a premium, and what still applies while a customization is switched off.
Best for: Seeing what is actually driving a listing’s prices before you change anything.
Example: “What pricing rules are set on Sunset Villa?”
update_customizations
Creates or updates customizations on one listing, group, or account. Requires OAuth customization write access, which is granted separately from write access — a connection that can change prices cannot change pricing rules unless customization write was granted too. A connection without it gets a 403 on this tool and is unaffected on every other one.
Everything in a single request is applied together or rejected together, so one invalid value fails every customization in that call. A rejected call comes back with the schema for what you tried to send, so the retry can be built from it rather than guessed.
A successful call describes each saved setting back in the same words get_customizations uses. Worth reading rather than skipping: percentages are signed, and a positive value is a premium rather than a discount. Nothing rejects the wrong sign, because a premium is a legitimate setting, so the echo is what tells you a 15% discount was saved as a 15% premium.
Switching a customization off does not mean no adjustment. It removes your rule and lets PriceLabs’ own pricing take over — turn off last minute prices and the algorithm’s market-driven discount applies instead. To have no last minute or far out adjustment at all, leave the customization on and set its type to none.
Switching off also affects saved settings differently per customization: last minute prices and far out premium reset their configuration, so re-enabling later means sending the full configuration again, while day of week adjustments keep the stored day values.
Best for: Applying a pricing rule across a group, or adjusting one listing’s seasonality from chat.
Example: “Make weekends 25% more expensive on Sunset Villa”
get_customization_schema
Describes how to write one or more customizations: the field names, the values each one accepts and what they mean, valid ranges, which fields a given type requires, and what switching it off does. Ask for every customization you plan to change in one call.
It comes straight from the Customer API specification, so it stays in step with what the API actually accepts. It describes no particular account, so no listing is needed.
Best for: Building a correct update_customizations call the first time.
Example: “What can I set on last minute prices?”
get_customization_profiles
Lists the saved profiles on your account — minimum stay, pricing, and check-in/check-out — with the ids that a custom seasonal profile points at. Can be filtered by type, by name, or to archived profiles only.
Best for: Finding the profile id to attach to a season before calling update_customizations.
Example: “Which pricing profiles do I have saved?”