Best Looks / Outpost — public API reference (plain text)
========================================================
This file is served as static text at:
  https://www.bestlooks.net/api-documentation.txt
Companion static page (HTML, also no JS required):
  https://www.bestlooks.net/api-documentation.html
Use either when automated tools cannot execute the SPA at /api-documentation
(that route returns a Vue shell; schema is not in the initial HTML).
Linked from index.html as rel=alternate (text/plain and text/html) for discovery.

If this URL fails in a third-party “web tool” (e.g. cache miss), fetch the site
homepage HTML instead: the same trip-planning summary is embedded inside the
<noscript> block of index.html (search for api-reference-static or
/v1/trip-planning).

If curl or a browser tool fails with “Could not resolve host” (curl exit 6)
----------------------------------------------------------------------------
That is DNS/network resolution failing inside the tester’s environment (e.g.
some LLM sandboxes block outbound DNS or cannot reach the public internet).
It does not prove the domain is invalid. From a normal laptop or phone on the
public internet, the same URL may resolve fine.

What to do when automated tools cannot fetch this URL:
  • Paste the full text of this file (or the trip-planning section) into the
    assistant instead of asking it to curl the live host.
  • Use the API base URL below; the app is configured for the www hostname.

API base URL (use this exact host in curl)
------------------------------------------
  https://www.bestlooks.net
  (Apex http://bestlooks.net/ or https://bestlooks.net/ may redirect to www;
   call the API on https://www.bestlooks.net to avoid cross-origin mismatches.)

TRIP PLANNING — copy/paste facts (verified in repo)
---------------------------------------------------
  Method:     POST
  Path:       /v1/trip-planning
  Full URL:   https://www.bestlooks.net/v1/trip-planning
  Headers:    Content-Type: application/json
              Authorization: Bearer <token>   (optional on this route in current server; rate limits apply)

  Required JSON field:
    location   (string) — region or route, e.g. "Italy: Rome, Florence, Venice"

  Common optional fields:
    startDate, endDate     ISO dates YYYY-MM-DD
    preferences            string or object — put interests, pace, hotels, constraints here
    budget                 number (total, major currency) recommended for predictable behavior
    language, originalQueryLanguage   e.g. "English"
    chatHistory            array of { role, content } for follow-ups / refinements

All documented routes use HTTP POST with JSON bodies unless noted.
Send header: Content-Type: application/json

Fields that assistants often invent — NOT this API’s trip-planning body
----------------------------------------------------------------------
  destination, trip_name, duration_days, start_city, destinations[],
  travel_style, interests[], pace, transportation_preferences[],
  hotel_preferences{}, constraints{}, output_format, notes
  …are not read as first-class keys by POST /v1/trip-planning. Put that
  information inside "preferences" (string or structured object) and use
  startDate/endDate for the window (or describe dates inside preferences).

Authentication
--------------
The interactive docs page states that endpoints expect proper authentication
headers. In the current backend, POST /v1/trip-planning and the other
documented /v1 routes listed below are not wrapped in JWT middleware; they
are subject to rate limiting in production. If you have a session JWT from
the web app, you may send Authorization: Bearer <token>; it is optional
for these documented POST endpoints unless your deployment adds stricter
rules.

Documented POST /v1 endpoints (keep in sync with /api-documentation)
--------------------------------------------------------------------
  POST /v1/extract-parameters
  POST /v1/translate
  POST /v1/format-query
  POST /v1/google-business
  POST /v1/google-reviews
  POST /v1/consumer-products
  POST /v1/trip-planning
  POST /v1/breaking-news
  POST /v1/events-nightlife
  POST /v1/documentation-issues
  POST /v1/travel-scams
  POST /v1/crime-statistics
  POST /v1/hospital-recommendations
  POST /v1/medical-diagnosis
  POST /v1/insurance-authorization
  POST /v1/medical-legal-assistance
  POST /v1/travel-emergency
  POST /v1/sora-prompt

There is NO public documented path such as /v1/itinerary-refine,
/v1/hotels-only, or /v1/dining-only with a trip_id. To refine an itinerary
or ask follow-ups, use POST /v1/trip-planning again with an updated
"chatHistory" array (and the same or revised location/dates/preferences).

--------------------------------------------------------------------
POST /v1/trip-planning — request body (documented shape)
--------------------------------------------------------------------
Required:
  location          string   Primary destination or region.

Optional:
  dates             string   Human-readable date range (often set by the SPA).
  startDate         string   ISO date YYYY-MM-DD (preferred for direct API calls).
  endDate           string   ISO date YYYY-MM-DD (preferred for direct API calls).
  preferences       string OR object  Free-text or structured preferences.
  budget            number or string  Total trip budget; backend logic often
                        expects a numeric total in major currency units.
                        If omitted, a high default may apply—set an explicit
                        number for predictable behavior.
  originalQueryLanguage  string  Language of the user's original query.
  language          string   Response language (originalQueryLanguage overrides
                        when both are sent).
  chatHistory       array    Prior turns for follow-up / refinement.
  provider          string   Optional model or provider hint.
  sessionId         string   Optional session correlation id.

Example response shape (abbreviated):
  { "message": "string", "data": { "chat_data": [ ... ], "metadata": {} } }

--------------------------------------------------------------------
Italy — three equivalent styles (all POST /v1/trip-planning, real fields)
--------------------------------------------------------------------
A) “Highlights” style (maps ChatGPT-style intent; adjust dates to your trip)

{
  "location": "Italy: Rome, Florence, Venice",
  "startDate": "2026-09-12",
  "endDate": "2026-09-21",
  "budget": 5500,
  "preferences": "Trip name: Italy Highlights. Balanced pace; mid-range budget. Destinations: Rome, Florence, Venice. Interests: food, history, art, walkable neighborhoods, scenic viewpoints. Transport: high-speed rail, minimal car use. Hotels: boutique or well-rated 4-star, central walkable. Constraints: avoid red-eye transfers; limit hotel changes. Request detailed day-by-day itinerary.",
  "language": "English",
  "originalQueryLanguage": "English"
}

B) First-time Italy, longer trip (set startDate/endDate to 12 consecutive days)

{
  "location": "Italy: Rome, Florence, Tuscany day trip, Venice",
  "startDate": "2026-06-01",
  "endDate": "2026-06-12",
  "budget": 6500,
  "preferences": "First Italy trip; cultural style; moderate pace; mid-range. Interests: architecture, museums, cafes, local food, photography. Prioritize iconic sights, strong food recommendations, efficient rail, one lighter day per city.",
  "language": "English",
  "originalQueryLanguage": "English"
}

C) South-leaning (10 days)

{
  "location": "Italy: Rome, Naples, Amalfi Coast",
  "startDate": "2026-09-01",
  "endDate": "2026-09-10",
  "budget": 6000,
  "preferences": "Trip: Italy South + Classics. Relaxed pace; mid-range; food-and-scenery. Interests: sea views, pizza, historic sites, relaxed evenings. Fewer hotel changes; scenic transport; strong restaurant picks.",
  "language": "English",
  "originalQueryLanguage": "English"
}

--------------------------------------------------------------------
Italy example — first request (10 days, 2 adults, Sept 12–21, 2026)
Rome → Florence/Tuscany → Venice; food, history, walkable areas, views
--------------------------------------------------------------------
Replace the URL host if you use a staging domain.

curl -sS -X POST "https://www.bestlooks.net/v1/trip-planning" \
  -H "Content-Type: application/json" \
  -d "$(cat <<'EOF'
{
  "location": "Italy: Rome, Florence, Venice",
  "startDate": "2026-09-12",
  "endDate": "2026-09-21",
  "budget": 5500,
  "preferences": "2 adults; moderate pace; mid-range lodging; focus on food, history, walkable neighborhoods, and scenic viewpoints. Route: Rome several days, then Florence with one Tuscan countryside day trip, then Venice. Prefer central 3–4 star hotels, breakfast included when possible, and high-speed rail between cities. Highlights to cover: Colosseum and Roman Forum, Vatican Museums, Trastevere evenings; Florence Duomo, Uffizi, Piazzale Michelangelo; Venice Grand Canal, Doge Palace, quieter sestieri. Avoid cramming every day and avoid 6am starts daily.",
  "language": "English",
  "originalQueryLanguage": "English"
}
EOF
)"

Windows PowerShell (single line body example):
  Invoke-RestMethod -Uri "https://www.bestlooks.net/v1/trip-planning" `
    -Method POST -ContentType "application/json" `
    -Body '{"location":"Italy: Rome, Florence, Venice","startDate":"2026-09-12","endDate":"2026-09-21","budget":5500,"preferences":"2 adults; moderate pace; ...","language":"English","originalQueryLanguage":"English"}'

--------------------------------------------------------------------
Follow-up: slower, more romantic (same endpoint, chatHistory)
--------------------------------------------------------------------
After the first response, send another POST /v1/trip-planning with prior
messages in chatHistory and a new user message in the last element (exact
schema depends on your client; the backend reads chatHistory for context).

Conceptual payload:

{
  "location": "Italy: Rome, Florence, Venice",
  "startDate": "2026-09-12",
  "endDate": "2026-09-21",
  "budget": 5500,
  "preferences": "Same trip as before.",
  "language": "English",
  "originalQueryLanguage": "English",
  "chatHistory": [
    { "role": "assistant", "content": "<paste prior assistant message>" },
    { "role": "user", "content": "Slow the itinerary down. Add more aperitivo time, sunset viewpoints, and one relaxed half-day per city. Keep cities and budget." }
  ]
}

(Adjust role/content field names to match what your client already sends;
the server merges chat history for date and intent extraction.)

--------------------------------------------------------------------
Follow-up: replace Venice with Amalfi Coast — still POST /v1/trip-planning
--------------------------------------------------------------------
Use chatHistory with a user message such as:
  "Replace Venice with 3 nights on the Amalfi Coast. Keep 10 days total
   and mid-range budget."

--------------------------------------------------------------------
Hotels-only or restaurants-only requests
--------------------------------------------------------------------
There is no separate documented hotel or dining endpoint. Encode the ask
in "preferences" and/or the last chatHistory user message on
POST /v1/trip-planning, e.g. "Return only hotel suggestions for Rome,
Florence, Venice with ..." or "List 5 lunch and 5 dinner spots per city ...".

--------------------------------------------------------------------
Human-readable interactive docs
--------------------------------------------------------------------
  https://www.bestlooks.net/api-documentation

Machine-readable (this file)
--------------------------------------------------------------------
  https://www.bestlooks.net/api-documentation.txt