Overview

The Wander REST API gives you read access to your published destination maps, points of interest (POIs), curated lists, and events. Use it to bring destination content into your website, app, or integration.

Base URL

The API base URL is assigned below. The examples in this reference use it as BASE_URL:

export BASE_URL="https://api.wander-app.com/api"

Scope

The API is scoped to your destination. Endpoints take a map ID or organization (publisher) ID that you own; these IDs are provided by your Wander contact or are visible in the builder. Wander-wide discovery and search are not part of the public API.

Most endpoints reject unknown or misspelled query parameters with a 400 response; a few ignore them. Send only the parameters documented in this reference.

Responses are JSON. Resource identifiers such as map, publisher, marker, list, and event IDs are UUIDs unless an endpoint says otherwise. Wherever a path takes :map_id, you can also pass the map’s slug (its alternative_id, such as explore-julian), except on GET /maps/:map_id/contents, which needs the UUID. Category and tag IDs are strings, such as keywordoutdoorrecreationtypestatepark.

The examples in this reference use the Explore Julian map, so you can run them as they are:

curl "$BASE_URL/maps/explore-julian/details"

Wander may add fields to responses over time. Read the fields your integration needs and ignore unknown fields so additions do not break your application.