FibAdvisor
An internal, wire-faithful twin of the TripAdvisor Content API
(api.content.tripadvisor.com/api/v1). Point a TripAdvisor client at this host by
swapping the base URL — responses match the real API's shapes, caps, and error envelope.
Faithful read API (key in the ?key= query param)
| Endpoint | Returns |
|---|---|
GET /api/v1/location/search?key=&searchQuery= | ≤10 trimmed matches |
GET /api/v1/location/nearby_search?key=&latLong= | ≤10 nearby matches |
GET /api/v1/location/{id}/details?key= | full flat location object |
GET /api/v1/location/{id}/reviews?key= | ≤5 newest reviews |
GET /api/v1/location/{id}/photos?key= | ≤5 photos |
Auth is an API key passed as ?key= (no bearer header, no OAuth),
optionally restricted by a Referer-domain or IP-CIDR allow-list. The bundled
rosie dev key is unrestricted.
⚠️ Synthetic management API — /mgmt/v1 (NOT real TripAdvisor)
Real TripAdvisor has no public API to reply to reviews — owner responses
happen only in the web Management Center. This
/mgmt/v1 surface is a
fictional reply contract so rosie can build & test its reply pipeline
today. In production, rosie should draft-and-deep-link the owner into the Management
Center instead. See the reference and docs/deviations.md.
POST /mgmt/v1/location/{id}/reviews/{reviewId}/response | upsert an owner response |
DELETE /mgmt/v1/location/{id}/reviews/{reviewId}/response | remove it |
Attribution
Faithful responses carry rating_image_url (the bubble graphic),
web_url/url (link-back), and review/photo attribution — so a client
can satisfy TripAdvisor's Display Requirements unchanged.