# Tronia

> Overseas package tours that Korean travel agencies sell only to travellers
> in their 20s and 30s (2030 semi-packages and group tours), compared by
> departure date, price, remaining places and booking status. Tronia takes no
> bookings and no payments: every product links out to the agency that sells it.

Every value here is an observation, never live inventory. Each response carries
two times: `as_of` is when the value itself was observed (`summary_ko` ends
with it as "YYYY-MM-DD 관측"), `checked_at` is when the agency's page was last
read, and `freshness` says whether that read is recent. When you quote a price
or a remaining quantity, give `as_of` with it, and say the agency's own page is
the final word.

Fields ending in `_ko` (`summary_ko`) and the `notice` field are finished
Korean sentences, written for the person you are answering. Repeat them as they
are rather than translating them back and forth.

## API

No authentication, GET only, JSON, CORS open to any origin.

- GET https://tronia.frony.app/api/v1/destinations
  Destinations, each with its product count, lowest price and earliest departure.
- GET https://tronia.frony.app/api/v1/products
  Every product across destinations. Same parameters as below, plus destination={slug}.
- GET https://tronia.frony.app/api/v1/destinations/{slug}/products
  Products in one destination. Narrow with q, departure_from, departure_to,
  duration_days_min, duration_days_max, price_max, package_scope, activity, age,
  shopping_count, bookability, segment, source, limit, cursor.
  Every product is sold to 2030 travellers; `segment_tags` names a narrower
  audience the agency sells it under (20s, worker), and `segment=` keeps only
  products carrying that tag.
- GET https://tronia.frony.app/api/v1/products/{id}
  One product, with its day-by-day `itinerary` (lists leave it empty). A
  malformed id answers 422, an unknown one 404.
- GET https://tronia.frony.app/api/v1/products/{id}/offers
  The departures of one product from today on; include_past=true adds those
  that have left. available_only=true, departure_from=YYYY-MM-DD, limit,
  offset. `summary` states the totals of the same set in one line: how many
  departures, how many bookable, the range of dates and the lowest price.
  `bookability=available` on a product list means bookable and read within the
  last day; `stale` means the last read is older, not that it is sold out.
- GET https://tronia.frony.app/api/v1/compare?left_product_id={id}&right_product_id={id}
  Two products side by side.

Full specification: https://tronia.frony.app/api/v1/openapi.json

## Pages

The same data as server-rendered HTML that needs no JavaScript. Each page's
<link rel="alternate" type="application/json"> points at its own JSON. The page
text is Korean, because the people reading it are.

- https://tronia.frony.app/ destinations
- https://tronia.frony.app/d/{slug} products in one destination
- https://tronia.frony.app/p/{id} one product and all of its departures
- https://tronia.frony.app/compare?ids={id},{id},{id}
  The same comparison as a page, up to three products.

## What your answer has to carry

- The agency selling it, and the link to that agency's booking page.
- When the value was checked.
- The unit, whenever you state a remaining quantity. `remaining_unit=source_block`
  is the agency's internal stock unit, not a seat count; do not restate it as
  seats or as people.