How much is a round trip from Jeju to Busan?

Set the two dates above and the search answers it for those dates. There is no fixed number to print here: a return fare is a function of when you go and how long you stay, and any figure written into this page would be stale by the time you read it.

Why is this not just two one-way searches?

Because airlines price a return as one product. The total of two one-way fares is frequently higher than the return fare, and occasionally lower than anything actually on sale. This calls the round-trip endpoint, which returns paired legs and a real total for the pair.

What does each row contain?

total_price and total_price_as_number for the itinerary, then the outbound leg and the return leg separately, each with its own airline, stop count, duration and times. That is how you tell a cheap total with a long layover apart from a cheap total without one.

Does trip length change the price?

Often, and sometimes by more than moving the outbound date does. Change the return date and run it again; each run is one request. Sweeping several trip lengths at once is a job for your own key, in parallel.

The search came back empty. What does that mean?

On a round trip it usually means the pair of dates cannot be flown as an itinerary, not that the route has no flights. The API says so through X-Search-Status: "empty" is a real answer, "degraded" means the search did not finish and would be retried.

Can I run the PUS to CJU direction?

Yes, swap the codes in the form. The endpoint does not care which end you start from.

Free tool · live search, rate-limited

Round trip Jeju to Busan

Out and back on CJU → PUS, priced as one itinerary. Both legs, their airlines and their stops, and one total for the pair rather than two searches you add up and hope match.

CJU ⇄ PUS

nothing searched yet

Set two dates and press Price the trip. Each row that comes back is one itinerary: the outbound and the return with their own airlines, stops and durations, and one total price for the pair. No stale sample sits here in the meantime, because a fare captured last month is not information.

Price out-and-back trips from your own code

One request, one itinerary list: paired legs with a real total, not two one-way searches you add together and hope match.

The marketplace host you subscribe on. The key in the snippet is your RapidAPI key.

curl -X POST "https://google-flights-live-api.p.rapidapi.com/api/google_flights/roundtrip/v1" \
  -H "Content-Type: application/json" \
  -H "x-rapidapi-host: google-flights-live-api.p.rapidapi.com" \
  -H "x-rapidapi-key: $RAPIDAPI_KEY" \
  -d '{
    "from_airport": "CJU",
    "to_airport": "PUS",
    "departure_date": "2026-10-02",
    "return_date": "2026-10-09",
    "currency": "usd"
  }'

Get your free RapidAPI key →Five-minute quickstart Read the docs

This route

CJU → PUS, in facts rather than adjectives

Airport names, countries and time zones come from the OurAirports-derived airport dataset. The distance is great-circle, computed from those two coordinate pairs. Prices are not here because a price that is not live is not a price.

Origin

Jeju International AirportCJU · Jeju, South Korea

Destination

Gimhae International AirportPUS · Busan, South Korea

Great-circle distance

291 km181 miles between the two airports

Time zones

Asia/Seoulto Asia/Seoul

Search type

DomesticBoth airports are in South Korea. The request is identical either way: two IATA codes and a date.

Why this page exists

busiest routes by available seats, 2025Rank 22 in that published table. We build a page for a route people actually fly, and only for those.

Reading the result

The total is only half the answer

Two itineraries with the same total can be very different trips, and the response says which is which.

Each row gives you the outbound leg and the return leg separately: airline, stops, duration and the times, on both sides. At 291 km between CJU and PUS, a connection adds real hours, and the row shows you where they go rather than burying them in a single total.

Trip length is the other lever. The return date is a field, so a week against ten days is two requests, not two different tools. If the difference matters to you, sweep it: that is the same call in a loop on your own key.

Nothing here is an average or a prediction. It is the itineraries that came back for the two dates you chose, at the moment you asked.

On your own key

One CJU → PUS trip here. Every trip length, on your key

Paired-leg pricing across a range of return dates is the request on this page, fired in parallel.

Round-trip docs Five-minute quickstart See pricing on RapidAPI →

Same route, different question

Three ways to look at CJU → PUS

Cheapest Time to Fly: CJU → PUS

Which month is cheapest, a year at a glance

Flight Price Checker: CJU → PUS

One date, the live fare and Google’s verdict

Routes next door

Other pages through CJU and PUS

Every one of these is in the same published ranking, and every one runs the same live search.

CJU → GMP

Jeju to Seoul

GMP → PUS

Seoul to Busan

The full list of route and city pages is on the tools index.

Questions, answered plainly

How much is a round trip from Jeju to Busan?: Set the two dates above and the search answers it for those dates. There is no fixed number to print here: a return fare is a function of when you go and how long you stay, and any figure written into this page would be stale by the time you read it.
Why is this not just two one-way searches?: Because airlines price a return as one product. The total of two one-way fares is frequently higher than the return fare, and occasionally lower than anything actually on sale. This calls the round-trip endpoint, which returns paired legs and a real total for the pair.
What does each row contain?: total_price and total_price_as_number for the itinerary, then the outbound leg and the return leg separately, each with its own airline, stop count, duration and times. That is how you tell a cheap total with a long layover apart from a cheap total without one.
Does trip length change the price?: Often, and sometimes by more than moving the outbound date does. Change the return date and run it again; each run is one request. Sweeping several trip lengths at once is a job for your own key, in parallel.
The search came back empty. What does that mean?: On a round trip it usually means the pair of dates cannot be flown as an itinerary, not that the route has no flights. The API says so through X-Search-Status: "empty" is a real answer, "degraded" means the search did not finish and would be retried.
Can I run the PUS to CJU direction?: Yes, swap the codes in the form. The endpoint does not care which end you start from.

Keep going

The rest of the toolkit

Any other route

The same planner, empty form

Which month is cheapest

A year of CJU → PUS in one chart

Free MCP server

Ask your assistant instead. No key, ad-supported

Round-trip endpoint

Field names and response shape