Routeless connects iGMS vacation-rental data to custom marketplaces through OAuth, property and listing mapping, calendar synchronization, and booking writes. Furnished Habitat verifies webhook signatures before updating local availability, prevents duplicate event processing, and keeps the external reservation identifier on confirmed bookings. Scheduled reconciliation remains separate from event-driven updates.
Evidence verified 2026-09-28 · Vendor facts reviewed 2026-09-28
Furnished Habitat contains a working iGMS connection for OAuth, property mapping, calendar and booking synchronization, signed webhooks, and direct-booking writes.
The evidence supports custom marketplace and calendar workflows for vacation rentals. It does not establish iGMS partnership status or continuous synchronization in every deployment environment.
A host authorizes iGMS, imports the account's property and listing identifiers, and maps those records to Furnished Habitat listings.
Evidence: Verified in the iGMS OAuth service, web callback route, connection model, and listing-mapping endpoints.
Initial, manual, scheduled, and webhook-triggered jobs fetch calendar windows, normalize occupied dates and reservations, and replace the matching local range used by availability checks.
Evidence: Verified in the iGMS sync service, recurring tasks, availability service, and calendar tables.
Confirmed marketplace bookings are sent to the mapped iGMS property and retain the returned reservation code. Host blocks can update the external property calendar through the calendar-control scope.
Evidence: Verified in the Furnished Habitat booking, availability, and iGMS integration services.
Hosts authorize the iGMS application through OAuth. Connection credentials remain server-side, and signed inbound events are validated before calendar or booking data is changed.
OAuth and webhook credentials remain in server-only configuration. Each host connection is scoped separately and does not expose iGMS credentials to browser code.
Rejected authorization prompts a reconnect instead of repeated calls with an invalid credential. Invalid webhook signatures are rejected, while failed booking updates remain visible for controlled recovery.
A furnished-stay marketplace with iGMS account connections, mapped inventory, calendar synchronization, and direct-booking writes.
Yes. Routeless implemented iGMS OAuth, property mapping, calendar synchronization, signed webhook handling, and direct-booking writes for Furnished Habitat. Vendor access and the exact iGMS scopes still need confirmation during scoping.
The verified receiver checks the sender, event age, and vendor signature before processing a webhook. Duplicate event identifiers do not repeat the same synchronization work.
No. Webhooks reduce delay, but scheduled reconciliation still catches missed events, revoked connections, and records that changed while a receiver was unavailable. The two paths should use the same mappings and idempotency rules.
An authorization failure marks the connection for reconnection. The system does not keep calling iGMS with a credential the vendor has rejected.
iGMS official site. The iGMS name and logo belong to their owner. Inclusion documents Routeless implementation experience and does not imply partnership, certification, or endorsement.
Share the account access, records, expected events, and the workflow that must recover when delivery fails.