Uplisting issues a single API key per account, with full scope. Rotating it breaks every existing integration simultaneously, including any other tools you have connected. Coordinate before rotating.
PX has read-only access. Nothing is written back.Properties - id, name, address, bedrooms / bathrooms / max guests, property type, currency, active flag, thumbnail.
Synced on connect, on listing webhooks, and on Properties -> Sync from Uplisting.Owners - id, first / last name, email, phone, properties owned.
Synced with the parent property.Reservations - id, listing, status, check-in / check-out, booking date, guest details, guest count breakdown, channel and confirmation code, currency, totals.
Synced on demand, on booking webhooks, and during audits.Per-charge financial data - line amount and type (accommodation / cleaning / fee / tax / discount), taxable flag, per-night accommodation breakdown, per-reservation totals, payments.
Synced with the parent reservation; payments also via payment webhooks.Tax catalog - rates, names, applicability per listing.
Synced on Tax Configuration -> Refresh from PMS.Webhook events - booking created / updated / canceled, listing created / updated, payment received / refunded.
Admin status is red.
The API key is wrong or was rotated in Uplisting. Get the latest value and update PX.Other integrations broke after rotating the key.
Expected. Uplisting uses a single shared key. Update every integration that uses it, including PX.