Tripadvisor via Scavio for Openclaw

1. Create a Scavio account and obtain an API key. New accounts include 50 free credits with no card required.
2. Export the required environment variable:

export SCAVIO_API_KEY=sk_live_your_key

3. Use the API base URL https://api.scavio.dev and send the key as a bearer token:

curl -X POST https://api.scavio.dev/api/v1/tripadvisor/locations \\
  -H "Authorization: Bearer $SCAVIO_API_KEY" \\
  -H "Content-Type: application/json" \\
  -d '{"query":"Austin, Texas","limit":12}'

4. Install the optional Python SDK:

pip install scavio==0.15.0

5. Install the optional JavaScript SDK:

npm install [email protected]

6. Initialize an SDK client. Both SDKs read SCAVIO_API_KEY from the environment. Keep API keys in environment variables or a secret manager, never in source control.
7. Start every lookup at /locations; do not invent geo_id or location_id values. Use the returned IDs for search, location, and review requests.

All responses use the envelope { data, response_time, credits_used, credits_remaining }.

Identifier taxonomy

• geo_id identifies a Tripadvisor destination, city, or region and is required for geographic searches.
• location_id identifies an individual restaurant, hotel, or attraction.
• A GEO lookup result has a geo_id and a null location_id.
• A business result returns the geo_id plus location_id pair used by venue and review requests.
• IDs may appear as bare values, such as 30196 or 1899234, prefixed values such as g30196 or d1899234, or inside Tripadvisor URLs.
• Search returns 30 locations per page. Review page size is 15 for restaurants and 10 for hotels and attractions.
• locations supports a single response limit from 1 to 20; its limit parameter is not pagination.
• Review pages can overlap at boundaries, so downstream storage should enforce uniqueness on review_id.
• A page beyond the final search or review page returns a billed 404 rather than an empty result.