Verified integrations · Property operations

PriceLabs API integration development

Routeless integrates PriceLabs pricing data with custom vacation-rental software. Furnished Habitat maps marketplace listings to PriceLabs identifiers, stores daily rates and minimum stays, accepts signed connector callbacks, and falls back to a base listing rate when imported pricing becomes stale. The implementation separates the Customer API polling model from the native PMS connector model.

Evidence verified 2026-09-28 · Vendor facts reviewed 2026-09-28

Evidence boundary

What the implementation proves.

Furnished Habitat contains working PriceLabs Customer API and connector flows for listing mapping, date-level rates, minimum stays, signed callbacks, and stale-rate fallback.

The evidence covers dynamic-pricing data and PMS connector workflows. It does not establish PriceLabs partnership status or claim that every account has the connector enabled.

Verified capabilities

  • PriceLabs listing discovery and external listing mapping
  • Daily rate and minimum-stay synchronization
  • Native PMS connector calendar and reservation export
  • Signed price callbacks, idempotent webhook claims, and stale-rate fallback
Implemented workflows

How data moves through the integration.

Workflow 01

Map marketplace listings to PriceLabs

Hosts or administrators select PriceLabs listings, while automatic matching can use existing OwnerRez or iGMS identifiers to propose the correct external record.

Evidence: Verified in the Furnished Habitat PriceLabs mapping service and host administration routes.

Workflow 02

Resolve nightly pricing for search and quotes

Customer API responses or connector callbacks populate dated rates and minimum stays. Marketplace search and quote services resolve those values for the requested stay.

Evidence: Verified in the PriceLabs sync service, connector callback handler, daily-rate tables, and pricing resolver.

Workflow 03

Export PMS calendar and reservation state

The connector path queues listing, calendar, and reservation jobs from marketplace changes, then sends a combined view of local bookings, host blocks, OwnerRez dates, iGMS dates, and iCal occupancy.

Evidence: Verified in the PriceLabs connector service, export outbox, mapper, and recurring job processor.

Authentication and operations

Access, secrets, and recovery are part of the build.

Authentication model

The Customer API uses a server-side PriceLabs API key. The connector path uses a separately authorized account connection and verifies signed callbacks. Credentials are not exposed to browser code.

Credential handling

PriceLabs credentials stay in server-only configuration. Customer API access and host-authorized connector access remain separate because they have different permissions and data flows.

Failure behavior

Failed imports and connector updates remain visible for recovery. Invalid callbacks are rejected. If imported rates are too old, guest search uses the listing's documented base rate instead of presenting stale dynamic pricing.

Vendor and implementation constraints

Limits that affect the scope.

  • Customer API and connector are different productsThe Customer API reads PriceLabs account data with an API key. A native PMS integration has a separate authorization and callback model. The implementation does not treat those paths as interchangeable.
  • Rates need a freshness ruleA technically valid stored rate can still be operationally stale. Furnished Habitat ignores aged PriceLabs data after the configured window and uses the listing base rate instead.
  • Listing identity must be unambiguousA PriceLabs listing cannot be silently claimed by two marketplace listings. Mapping conflicts stop the connection and require an explicit correction.
Related production proof

Projects behind the claim.

Furnished Habitat

A marketplace pricing system with PriceLabs listing mapping, date-level rates, minimum stays, callback verification, and fallback behavior.

PriceLabs integration FAQ

Questions that change the implementation.

Yes, when PriceLabs approves and provisions the relevant access. Routeless has implemented both Customer API rate ingestion and a separate PMS connector architecture with listing, calendar, reservation, and callback workflows.

The Customer API lets an account read its PriceLabs listings and prices with an API key. A PMS or channel-manager integration uses a separate vendor relationship and synchronization contract. Authentication, data direction, and callback behavior differ.

Mappings can be selected manually or proposed from known external identifiers such as OwnerRez property IDs and iGMS property or listing IDs. The system rejects a mapping when that PriceLabs listing is already assigned elsewhere.

Furnished Habitat checks when PriceLabs data was refreshed. If the data exceeds the configured age, the pricing resolver ignores it and uses the listing's base nightly rate rather than presenting an old dynamic rate as current.

Official sources

Vendor facts checked against current documentation.

PriceLabs official site. The PriceLabs name and logo belong to their owner. Inclusion documents Routeless implementation experience and does not imply partnership, certification, or endorsement.

Scope a PriceLabs integration.

Share the account access, records, expected events, and the workflow that must recover when delivery fails.