Roadtrippers Developer Hub

Welcome to the Roadtrippers Developer Hub. You'll find comprehensive guides and documentation to help you start working with Roadtrippers as quickly as possible, as well as support if you get stuck. Let's jump right in!

API Concepts


The primary data structure in the Boone API Suite is the place. A place is anything with geographic coordinates. So Orlando, Disney World, Space Mountain and the water fountain near Space Mountain are all places. Places can contain other places at any level.

Travel Place Code (TPC) / Canonical Place ID

All places in Boone are organized around the Travel Place Code (TPC), also called the canonical place ID. A TPC universally identifies places in the same way a UPC universally identifies a product.
As place’s TPC is persistent through

  • Moves
  • Changes of ownership
  • Non-essential name changes

Tag Taxonomy and Schema

Every place is marked with one or more tags. Tags are hierarchical, which means that higher level tags will be inferred from lower level tags (e.g. marking something as Chinese Food automatically includes the Asian Food and Food & Drink tags).

Tags can imply attributes at various levels. A place that is tagged as a Restaurant implies opening hours and when that same place is further tagged as a Japanese Steak House, that tag implies the existence of an attribute that also shows the presence of hibachi tables.

Standard Tags describes the tags that the Boone API Suite supports out of the box.


Sometimes there are more places that are returned by a query than could be presented/displayed to the user and it is necessary to rank them. Boone's TravelRank technology calculates a score for each place in the current view based on:

  • Social and cultural importance
  • Strength of ratings and reviews
  • Contextual relevance

Updated 2 years ago

API Concepts

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.