Sell our trips. $100 a booking.

The endpoints

• GET/api/v1/trips

  Every bookable trip, with the departures on sale, prices and seats remaining.

• GET/api/v1/departures/:id

  One departure: its four tiers, every add-on, what each costs.

• POST/api/v1/quote

  Price a configuration — travelers, rooms, tier, extras, a code. The same function the site runs, so your total always matches ours.

• POST/api/v1/custom-trips

  Describe a trip one of your customers wants. We research real hotels, price it and return a proposal plus the link their traveller opens.

• GET/api/v1/custom-trips

  Every proposal we have built for you, newest first.

• GET/api/v1/custom-trips/:id

  One proposal, read back. Ours is the copy that counts, so you never have to be the system of record for our price.

• POST/api/v1/custom-trips/:id/handoff

  A fresh link for the traveller. It retires the previous one, which is also how you revoke a link you sent by mistake.

Booking through the API is not open yet, and on a custom trip it never will be: the traveller pays us, on our checkout, because that is the arrangement our room rates are licensed under. What you get instead is the handoff link below.

Building an AI assistant? The same endpoints are an MCP server, with the same key: see For AI agents.

Custom trips

Tell us where one of your customers wants to go. We research real hotels on the dates they asked for, price the trip with our own model, and hand back a proposal you can put on your own site as powered by Guideless — your brand, your copy, your price on top of ours. The traveller books with us.

curl -X POST -H "Authorization: Bearer gl_live_…" \
  -H "Content-Type: application/json" \
  -d '{"action":"propose",
       "brief":{"destinations":["Nice","Seville, Spain"],
                "month":"2027-05","nights":7,"travelers":2,
                "budgetBand":"comfort","interests":["food"]}}' \
  https://guidelesstravel.com/api/v1/custom-trips

Either month + nights or startDate + endDate. budgetBand is value | comfort | premium | luxury. Write a city we do not run trips in as “City, Country” — there are two Valencias, and we ask rather than guess.

What comes back, and what never will

Per city: the hotel’s name, its star rating and its area, the nights, whether breakfast is included, and what cancelling it costs. Per trip: the price per traveller and in total, the cancellation terms, the rail, and the limitations.

Never: a rate id, a nightly price, a room type, a supplier name, what the room cost us or what our fee is. Not an oversight to ask us about — our room rates come from suppliers whose agreements let us sell travel to our own customers and nothing more, and that licence does not pass to you. It is the same line the rest of this API is drawn on.

The handoff

The existing bookingUrl field is a one-time handoff to the traveller's Guideless trip plan, with your attribution. It does not open checkout or hold rooms while checkoutAvailable is false. Treat priceStatus of planning_recheck_required as a request for a current room review. Ask for a new link at POST /api/v1/custom-trips/:id/handoff; the old one then stops working.

What you have to show them

Two fields on every proposal are ours to write and yours to pass on as written — summarising either of them into something friendlier is a breach of the Partner Agreement, and the traveller would be buying something we did not sell.

• cancellation — one statement for the trip, built from the rooms we actually hold and never more generous than the strictest of them. A custom trip can be entirely non-refundable; our catalogue tiers do not apply to one.
• limitations — what we are not doing, in plain words: a city we have never operated in, no transfer arranged, no local contact, recommendations nobody of ours has walked.
• rail[].note — we price trains on the routes we run. A leg we cannot price is named, excluded from the total and quoted separately. On a multi-city trip this is the limitation you will meet most often.

The proposal includes a price-validity timestamp, but that is not a room hold or a thirty-day price guarantee. We check current rooms, price and cancellation terms before a traveller can pay. Do not describe a planning proposal as held, booked or confirmed.

Limits

300 proposals an hour per key, and every call counts against your monthly ceiling like any other. Tighter than the reads because each one makes real supplier requests. One brief is capped at four cities and twenty-one nights — a bigger one is refused with a message naming the limit, never quietly trimmed to fit, because a traveller who asked for six cities and was shown four has been sold something else. Cache a proposal for up to an hour; the response says so.

Trying it

Every endpoint needs your key. A call without one — or with a revoked key, or on an account with no card on file — gets a 401 with a reason and a link back here, and is not billed.

curl -H "Authorization: Bearer gl_live_…" \
  https://guidelesstravel.com/api/v1/trips

curl -H "Authorization: Bearer gl_live_…" \
  https://guidelesstravel.com/api/v1/departures/<id>

curl -X POST -H "Authorization: Bearer gl_live_…" \
  -H "Content-Type: application/json" \
  -d '{"departureId":"<id>","roomIndexes":[1,1],"tierId":"<tier>"}' \
  https://guidelesstravel.com/api/v1/quote

Send your key as a bearer token or as X-API-Key. Keep it on your server; it is a credential.

Getting paid

Call us from your server, then send the traveller to us with your key’s prefix on the link. The prefix is the short public half of your key — safe on a URL, useless for calling the API — and it is what the commission follows:

https://guidelesstravel.com/tours/monaco-grand-prix?partner=gl_ab12

It sticks for ninety days, survives them browsing away and coming back, and pays out when the booking confirms.

On a custom trip you do not add anything: the proposal already knows you asked for it, so the handoff link attributes you on its own. Commission is paid after the departure has run, because that is when the money is genuinely ours and when a cancellation can no longer take it back.