TravelPad Connect API

Version 1.0 · Last updated: October 1, 2026

TravelPad Connect lets AI assistants plan road trips for people who use TravelPad. With one linked account, an assistant can map a drive, recommend real places to stop along the way, check the weather and daylight for the trip, and save the plan to the person's TravelPad account, ready to navigate in Google Maps.

Base URL

https://travelpad.travel/api/connect/v1

Authentication

OAuth 2.0 Authorization Code + PKCE

Format

JSON over HTTPS (TLS 1.2+)

OpenAPI 3.1 spec

/developers/openapi.yaml

What the API does

Everything a traveler can do in the TravelPad planner, as tools an assistant can call:

• Plan drives. Map a route from A to B with real distance and driving time, optionally avoiding highways or tolls.
• Recommend stops along the route. TravelPad's ranking finds well-reviewed places spread evenly along the drive, matched to the person's interests and ranked by how small the detour is. Search for anything specific too: "lunch around the halfway point", "EV chargers", "scenic viewpoints".
• Route intelligence. Weather moving across the route on the travel date, sunrise and sunset, an elevation profile, and a route quality score with suggestions.
• Save and organize. Save drives, add and reorder stops, and group drives into multi-day trips with dates.
• Community knowledge. Browse road trips other travelers have shared and read their on-the-ground tips about places.
• Hand-off links. Every drive comes with a Google Maps link containing every stop for turn-by-turn navigation, and a TravelPad link to the full plan.

Quickstart

A typical conversation ("Plan a drive from Denver to Moab with a couple of good hikes") takes three calls once the account is linked.

1. Create the drive

curl -X POST https://travelpad.travel/api/connect/v1/drives \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: 3f1c9a52-7d0e-4c6b-9a1e-2b8f5d4e6a10" \
  -d '{ "start": { "text": "Denver, CO" }, "end": { "text": "Moab, UT" } }'

2. Get recommendations

curl -X POST https://travelpad.travel/api/connect/v1/recommendations \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "driveId": 4821, "query": "hiking trail", "limit": 3 }'

{
  "driveId": 4821,
  "route": { "distanceMeters": 569700, "durationSeconds": 19920,
             "distanceText": "354 mi", "durationText": "5 hr 32 min" },
  "recommendations": [
    {
      "googlePlaceId": "ChIJt-6zQ0pSR4cRZ9kz8mT7cGE",
      "name": "Hanging Lake Trailhead",
      "reason": "Hiking · ~2 hr 40 min in · 4.8★ from 6,100 reviews",
      "address": "Hanging Lake Trail, Glenwood Springs, CO 81601",
      "latitude": 39.6014, "longitude": -107.1918,
      "category": "nature", "rating": 4.8, "ratingCount": 6100,
      "routeFraction": 0.46, "detourMinutes": 6, "detourIsEstimate": false,
      "googleMapsUrl": "https://www.google.com/maps/search/?api=1&query_place_id=ChIJt-6zQ0pSR4cRZ9kz8mT7cGE"
    }
  ],
  "count": 1,
  "remaining": 2
}

3. Add the stops the person likes

curl -X POST https://travelpad.travel/api/connect/v1/drives/4821/stops \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "googlePlaceId": "ChIJt-6zQ0pSR4cRZ9kz8mT7cGE" }'

The response is the updated drive. Share links.googleMapsUrl for navigation and links.travelpadUrl for the full plan.

Authentication & account linking

Every endpoint acts on behalf of one TravelPad user, so every request needs an OAuth 2.0 access token. TravelPad implements the Authorization Code flow with PKCE (S256), per RFC 6749 and RFC 7636.

How linking works for the person

1. The assistant sends the person to the authorization URL.
2. The person signs in to TravelPad, or creates a free account on the spot.
3. A consent screen lists exactly what the assistant is asking to do. The person approves or declines.
4. TravelPad redirects back with a one-time code, which the assistant exchanges for tokens.

People can see and disconnect linked assistants at any time from their TravelPad account settings. Disconnecting revokes all tokens immediately.

Exchanging the code

curl -X POST https://travelpad.travel/oauth2/token \
  -u "$CLIENT_ID:$CLIENT_SECRET" \
  -d grant_type=authorization_code \
  -d code=$CODE \
  -d redirect_uri=$REDIRECT_URI \
  -d code_verifier=$CODE_VERIFIER

{
  "access_token": "eyJraWQiOi...",
  "refresh_token": "kT9xQ2...",
  "token_type": "Bearer",
  "expires_in": 3600,
  "scope": "profile:read drives:read drives:write trips:read trips:write community:read"
}

Send the access token on every request: Authorization: Bearer <access_token>. Client credentials are issued by TravelPad to approved partners; email hello@travelpad.travel with your redirect URIs.

Scopes

The API never exposes email addresses, passwords, payment details, direct messages, or the ability to delete drives, trips, or the account.

Requests & responses

• Request and response bodies are JSON (Content-Type: application/json), UTF-8.
• Distances are in meters, durations in seconds, and every response also includes human-readable distanceText / durationText (US units).
• Dates are YYYY-MM-DD; timestamps are ISO 8601 in UTC.
• Locations are passed as a LocationInput object with one of: text (free text such as "Zion National Park"), googlePlaceId, or latitude + longitude.
• routeFraction describes where something sits along a drive: 0 is the start, 0.5 halfway, 1 the destination.
• Pagination: list endpoints accept limit and cursor and return nextCursor (null on the last page).
• Idempotency: endpoints that create things accept an Idempotency-Key header. Retrying with the same key within 24 hours returns the original result instead of a duplicate.
• Every response carries an X-Request-Id header. Include it when contacting support.

Errors

Errors use standard HTTP status codes and one consistent body. message is plain English and safe to show to the person.

{
  "error": {
    "code": "PLAN_LIMIT_REACHED",
    "message": "Free accounts can save 5 drives. Upgrade to TravelPad Pro for unlimited drives.",
    "upgradeUrl": "https://travelpad.travel/pro"
  }
}

Rate & plan limits

Rate limits apply per linked account: 60 requests per minute, of which at most 20 may be getStopRecommendations calls. Every response includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers.

Plan limits are the same as in the TravelPad app. Free accounts have a limited number of saved drives and trips, and a limited number of recommendation requests per drive. TravelPad Pro removes these limits. getMyProfile reports what the person has left, and getStopRecommendations returns remaining for the drive. Previews, route insights, and reading saved data never count against plan limits.

Endpoint reference

All paths are relative to https://travelpad.travel/api/connect/v1. Full request and response schemas are in the OpenAPI specification.

Account

Places

Routes

{ "driveId": 4821, "date": "2026-10-17" }

Recommendations

Drives

Trips

Community

Data use & privacy

• The API only acts for the person who linked their account, within the scopes they approved.
• Community content is limited to what travelers chose to share publicly. Other people's email addresses and private drives are never returned.
• TravelPad doesn't sell personal data or use connector traffic for advertising. Request logs are kept for 30 days for security and debugging.
• Unlinking from TravelPad account settings revokes all tokens for that assistant immediately. Deleting a TravelPad account revokes everything and deletes the person's data.

The full policy is in the Privacy Policy; use of the API is subject to the Terms of Service.

Support & status

Questions, partner credentials, or a bug report: hello@travelpad.travel. Include the X-Request-Id from the response.

The API is versioned in the path (/v1). Breaking changes ship as a new version, with at least 90 days' notice before an old version is retired. Additive changes (new fields, new endpoints) can happen at any time, so clients should ignore fields they don't recognize.