Developers
Build on your official map.
Embeds, a small JavaScript SDK, a public read-only API and a server that connects Claude to your map: what your web team or agency needs to put your Wander map to work on your own website. All of it is documented at developer.wandermaps.com.
Site embed
Let every page steer the map.
Put your official map beside every page of your website. Each page tells the map what it’s about: an article shows only the places it mentions, and a home page keeps the whole destination in view while lifting out the places its tiles feature. Change the places and the site embed follows without reloading.
- Photo pins and numbered stops for the places a page is about.
- Connected places, such as the parking for a trail, drawn the way your team has linked them.
- Search inside the map: your places first, and places you haven’t mapped can turn up under “Elsewhere”.
- Events back to your page when someone taps, searches or selects a place, so your page can answer.
The SDK is pre-1.0, so its API may change before 1.0. Letting pages steer the map needs a developer: the builder’s Site embed card gives you a plain iframe that isn’t page-aware.
<div id="map"></div>
<script
src="https://developer.wandermaps.com/sdk/wander-embed-0.7.1.js"
integrity="sha384-GrP87/AQqfot4VXeIvWCLiae39xyYwRc/a/xOkfOYPLhdR+lok8ducTwShp9IPT9"
crossorigin="anonymous"></script>
<script>
// This page is about two places: feature them.
const site = Wander.siteMap('#map', {
mapId: 'YOUR_MAP_ID',
mode: 'emphasize',
context: [
{ poiId: 'FIRST_PLACE_ID', role: 'featured', badge: '1' },
{ poiId: 'SECOND_PLACE_ID', role: 'featured', badge: '2' }
]
});
// A tap on the map can drive your page, too.
site.on('poiSelected', (e) => openPlace(e.poiId));
</script>Five embeds, one map.
Every embed is an iframe served from web.wander-app.com. Copy the code from the Wander builder or build the URL yourself. You only need the SDK when your page should steer the map.
- Site embed
/siteembed/{mapId}A page-aware map. Each page chooses which places show and which stand out. - List embed
/listembed/{mapId}An itinerary, tour or listing map: a hand-picked set of places, with routes when you want them. - Full map
/{mapId}Your complete map, with search, filters, place details and events. - Simple embed
/simpleembed/{mapId}One place in context, with a button to explore the rest of the map. - Events calendar
/eventsembed/{mapId}Your events as a list, a month or a week, with no map at all.
Embed SDK
One small script, pinned to the version you tested.
wander-embed.js mounts a site embed or a list embed and gives your page a JavaScript API: commands that move and focus the map, and events when people use it.
Your page can steer an itinerary or listing map too. Tap a listing and the map flies to it; switch days and the map follows. Camera, selection and day changes are instant. Changing the set of places reloads a list embed.
- Example
- 0.7.1, released September 23, 2026. Newer builds are listed, with their hashes, as they ship.
- Where it lives
- developer.wandermaps.com/sdk. There’s no npm package; you can also copy a versioned file into your own build.
- Pinning
- Versioned files never change. From 0.6.0 on, each build has a sha384 integrity hash, and the files are served with CORS enabled, so a pinned script tag loads.
- Status
- Pre-1.0: its API may change before 1.0.
- Without it
- Every embed also works as a plain iframe.
REST API
Your map’s content, as JSON.
The Wander REST API is public, read-only and scoped to your destination: you read your own published maps, places, lists and events by their IDs. Read endpoints need no authentication, so your site, app or CMS can call them directly.
- Maps
Map details, content blocks and your organization’s maps.
- POIs
Places, trails and areas, and the connections between them.
- Lists
Your published itineraries, tours and guides.
- Events
Your events, and what’s coming up at each place.
API keys: coming soon. Self-serve keys are on the way. Today’s public read endpoints don’t need one.
API referencecurl "https://api.wander-app.com/api/maps/c2025939-af64-4371-a281-c6818b2cd96e/markers"
[{
"data": {
"type": "FeatureCollection",
"features": [{
"geometry": { "type": "Point", "coordinates": [-77.6460873, 41.0239524] },
"properties": {
"name": "Bald Eagle State Park",
"address": "149 Main Park Rd, Howard, PA 16841, USA",
"phone": "(814) 625-2775",
"website": "https://www.dcnr.pa.gov/StateParks/…",
"updated_at": "2026-09-03T11:53:37.761Z"
}
}, …]
},
"category": { "id": "b02d39d2-716b-4a6f-92fd-7778d84d7de3" }
}, …]Integrations
Your listings in. Your places out.
Keep your map and your website telling the same story, without building the plumbing yourself. We set these up with your team.
Headless and custom CMS sites
- Out
- One call to your map’s feed returns every place pin with its address, website, phone and last-updated time.The places reference
- In
- On request, we can sync listings from a JSON feed your CMS already publishes.Set up by Wander
Simpleview and CRM sync
PilotKeep your listings in Simpleview or a CRM? Ask us about connecting it. The sync is designed to map your categories onto the map’s filters and pair each listing with its place by your own listing ID. The guides below describe how it works.
Wander MCP
Connect to Claude or ChatGPT.
The Wander MCP server connects Claude, or ChatGPT on Business, Enterprise and Edu plans, to your map, so your team can make changes in plain English: fill in details and photos for up to 100 places in one approved step, import trails from GeoJSON, or restyle your basemap. Most changes, and every deletion, are previewed before they’re saved.
More than 140 tools for destination teams. It needs a Wander organization account, and it works with any MCP client that supports OAuth sign-in, including Claude Code.
claude mcp add --transport http wander \
https://wander-mcp-dot-wander-production-308019.uc.r.appspot.com/mcpPlanning an integration?
Tell us what you’re building, and we’ll show your team how the pieces fit on a 30-minute call.