SimpleView

Wander offers a managed, read-only integration for destinations using SimpleView. Wander’s team connects to the SimpleView Listings API with credentials provisioned by your team, then reads published listings on a regular schedule. Your team does not install or operate the connection.

SimpleView cannot push listing changes to Wander, so there is no webhook to configure. Changes appear on the Wander map after the next scheduled sync. If a corrected listing needs attention sooner, contact your Wander partner manager to request an on-demand sync.

Stable listing IDs

SimpleView’s LISTINGID is stored in Wander as the listing’s external ID. It must remain stable because it keeps the SimpleView record paired with the same Wander place when names, addresses, or other details change.

Wander also recommends adding an account UDF named Wander Maps ID. Your team can record the Wander place UUID in that field as a durable cross-reference. Because SimpleView access is read-only, Wander does not populate the field automatically. A manually recorded value helps Wander’s team verify links; it is not currently used to create a link automatically.

Partner checklist

Before setup, work with your Wander partner manager to:

• Provision credentials that allow Wander to read published listings from the SimpleView Listings API.
• Review listing data quality, including accurate latitude and longitude or a complete address, useful categories, and current photos.
• Agree on how SimpleView fields map to Wander place fields.
• Agree on how SimpleView categories map to your Wander map’s tags.
• Decide which fields your source listings own and which fields Wander stewards may curate and protect from source updates.

Wander’s team handles the connection, synchronization, and monitoring after these decisions are in place. Your team’s ongoing role is to keep SimpleView listing data accurate and coordinate mapping changes with Wander.