add_trip_agenda_event
ChatGPTAdd an agenda (itinerary) event to one of the current user's trips. Returns the created event with its id.
add_trip_guests
ChatGPTAdd one or more guests to one of the current user's trips — the people attending it, who get a room. This is the right tool for any plain "add these people to the trip" request. A guest gets no access to the trip in Workgrounds: they cannot see the guest list, the rooms, the costs, or anything else the planner sees. Giving a colleague that access is grant_trip_planner_access, a different and much broader action — never reach for this tool to grant access, or that one to add an attendee. This only adds them to the guest list — it does NOT send any invitation email; the guests are not notified. Name and email are both optional. After adding, tell the user the guests are added-but-not-invited, and offer to send their invitations with invite_trip_guests. Duplicate emails (already on the trip, or repeated within this call) are skipped silently and returned in skipped_emails; only bring up skipping when that list is present.
archive_request
ChatGPTArchive one of the current user's room block requests (e.g. to undo a mistaken create). The user cannot undo this themselves — unarchiving is Workgrounds-staff-only — so confirm with them before calling it, and afterwards say that restoring it means asking Workgrounds.
ask_proposal_question
ChatGPTAsk the hotel a question about one of the current user's proposals (an inquiry) — anything about the property, the terms, or what they'd be willing to change. Use list_request_proposals to find the proposal id. Only 10 questions may ever be asked about a given proposal, so gather everything the user wants to know into one question rather than sending them one at a time — read the existing thread in get_proposal's questions first to see how many are already spent. NOT for asking for more time to decide: needing longer than the offer's expiration_date is request_proposal_extension, which is the only route that actually moves a deadline and costs none of the questions. Phrasing is not the test — "ask them if they can hold it until the 20th" is still an extension, not a question. It goes to the team to put to the hotel, so nothing comes back in this conversation and there is no timeframe to offer: say it has been put to them, and don't send the person off to watch the offer for a reply. Questions belong to sourcing, so a booked offer (booked=true) takes no more of them, and there is nothing equivalent on the trip it became — tell the user the thread is closed rather than reaching for a trip tool. Its request's other hotels are still open: a booked request keeps sourcing, and their unbooked offers take questions as usual.
assign_trip_rooms
ChatGPTGive named guests a room from one of the current user's trip room blocks. The guests hear nothing: no email and no message, so a guest who has not been invited still knows nothing about the trip — invite_trip_guests tells them, and its assign_rooms does the assigning and the telling from one confirmation. Every entry says who with guests and what with room_name, spelled as list_trip_rooms spells it; add check_in and check_out where free rooms of that name run over different dates. guests takes the filters list_trip_guests takes: ids names people one by one, and any other filter covers a group of any size, so {guests: {tag: "design"}, room_name: "Standard King"} seats the whole design team however many that is. Any guest can take any free room: nothing on a guest limits them to one room type. A filter other than ids takes only the guests who need a room and have none, and they come back counted per room type rather than listed. A room can be taken only while it is free — unassigned, and not waiting on the hotel — and each guest in the call takes a different one. Read the assignment out first: who it covers, the room type and its dates. Moving a guest to another room, or taking their room back, is done in the app on urls.guests.
create_request
ChatGPTCreate a room block request for the current user's org and submit it for sourcing — this notifies the selected hotels. The room block is given as nightly room counts, which is how hotels quote and how planners describe it; the server works out who arrives and leaves when. Optionally include event spaces, food & beverage, and questions for the hotels. Guest names are not part of this — attach a rooming list with set_request_rooming_list once the request exists, and assign guests to rooms with assign_trip_rooms once a proposal is booked. Takes two calls, and the first one creates nothing. Call it without confirm_token and you get back preview: the whole request as it would be sent — hotels named rather than id'd, the room block expanded to its real totals, the org it lands under, and every setting including the ones left empty. Read that preview out to the user, name anything in it you picked rather than were told, and get an explicit yes. Then call again with the same arguments plus the preview's confirm_token, and it is created. If the preview warns that an open request looks like the same trip, ask the user whether it is before confirming: one trip is one request, so if it is the same trip, change that request with update_request instead. accept_fewer_rooms, budget and book_by are never yours to guess, and neither is event_space_optional when you are asking for event space — ask about those. The rest you may fill in, so long as you name what you filled in when you read the preview out: it is there to catch your choices, not to excuse them. A confirmed call returns created: the request, a urls object — share urls.self so the user can watch the offers come in — and a hotels list naming and linking each hotel now being sourced. A user may create at most 5 requests in any 24 hours; past that this fails and the request has to be created in the app. Previewing costs nothing against that allowance — only a confirmed call does.
find_hotels
ChatGPTSearch Workgrounds' hotel inventory. Everything we hold is filterable and sortable, and every field you can filter on comes back on each row. Where: location + radius_miles (we geocode the location for you), or city / region / country. What: min_room_count / max_room_count, star rating, event-space capacity, area and count, and amenities. Which ones: name_any and address_any match any of your terms, name_all and address_all require all of them. In what order: sort by distance, room_count, star_rating, event_space_capacity, event_space_sq_ft or name, either direction. Start from any one of these — a place, a name, or an address is enough. get_hotel gives you everything we hold on a single hotel once you've picked one. Already have hotels in mind, from a web search, a conference page or the user's own words? Put the names straight into name_any, as many as you like in one call: each row tells you which of your terms it matched, and a match hands you the id to source that hotel with. Anything we didn't turn up comes back in unmatched_names — a long full name is one substring, so retry those as name_all with the words that distinguish the hotel (["ritz", "carlton"]) to catch them. The recommendation is yours to make. We give you the inventory and the levers; you know the trip, the group and what the user actually wants. Decide what matters, choose the filters and sort that serve it, run as many queries as it takes, read the rows, and tell the user why you picked these. What comes back is the sort you asked for, so present it as your shortlist and your reasoning. total is how much inventory matched in all — worth mentioning when there's much more than the page you're looking at. Every row carries its own url, so share that whenever you name a hotel and the user can look at it themselves; urls.search opens the same search in the app for them to browse and filter further.
get_guest_room_requests
ChatGPTList the guest requests waiting on the current user for one of their trips — guests asking to change or cancel their room. Read-only: shows what each guest is asking for. Approving or denying (and reading the guest's free-text note) is done in the app — share each request's review_url for that.
get_hotel
ChatGPTEverything we hold on one hotel, by id (from find_hotels): full address and coordinates, every event space with its size, amenities, and a description of the property. Reach for this on the hotels you're seriously considering, once find_hotels has narrowed things down.
get_my_invitation
ChatGPTEverything the current user can see about one trip they've been invited to (id from list_my_invitations): the hotel and its address, the trip's dates, what the planner wrote for guests, the published schedule, and where the guest stands on a room. my_reservation.status says whether a room is booked, waiting to be claimed, not needed, or still to come. These tools only read — claiming a room, asking to change or cancel it, adding self-paid nights and answering the planner all happen in the app, so hand over the matching url instead of offering to do it. Costs, invoices, the rest of the guest list and anything about how the trip was sourced are not a guest's to see and aren't returned.
get_my_profile
ChatGPTWho the current user is: their name, their email once verified, and the org they plan or travel for with their role there. org is null only for Workgrounds staff, so a null never means the caller works for Workgrounds. The answer holds for the whole conversation, so once is enough.
get_org_offices
ChatGPTThe places the current user's org works from, as they have recorded them: each office's name, address and coordinates. The user may call the org their company, their team, or their enterprise — those all mean the org. This is what a user means by "our office", "the London office", "near the team" or "close to us" — resolve any of those to an office here rather than guessing at a city. Every planner on the org can read this. To find hotels near one, pass its latitude and longitude straight to find_hotels with a radius_miles; that is more accurate than searching on the address text, and needs no geocoding. An office with no coordinates never resolved to a point, so search on its address instead. Offices are added and edited in the app, at urls.offices.
get_org_planners
ChatGPTList the planners on the current user's org: who they are, which of them are org admins, which are still sitting on an unaccepted invitation, and which have been deactivated. The user may call the org their company, their team, or their enterprise — those all mean the org. Only an admin on the org may call this; for everyone else it fails, and the way to give a colleague access is to name their email address directly. For an admin this is the set of colleagues who can be given access to a trip or request straight away — use it to turn a name the user mentions into the address grant_trip_planner_access and grant_request_planner_access take. A planner carrying deactivated is the exception: they are off the org and cannot be added to anything, so leave them out of any list of colleagues to choose from unless the user asks about them.
get_proposal
ChatGPTGet full terms for one proposal by id (from list_request_proposals): what the hotel is actually holding, plus room rates, fees, taxes, and cancellation/attrition policy. rooms_per_night, nights and event_spaces are the offer's own shape — read them against get_request to work out what the offer leaves out, since a hotel may come back with fewer rooms, different nights, or no event space, and the request says how much of that the user will accept. Every money field is already formatted for quoting, so pass it through as it stands and never do arithmetic on it: room_block_total is the rooms with their fees and taxes in, extras_total is event space, F&B and A/V with theirs, and booking_total is the two together, which is what offers carrying extras compare on. A money field that is absent is one the hotel put no figure on, except where totals_unavailable is true, which means the offer's money could not be worked out at all and this offer must not be compared on price. food_and_beverage carries the minimum the group commits to, and fine_print, event_space_details, each space's about, details and the differences_from_request note are where a hotel's own conditions live, so read them all before telling anyone a term is not in the offer. cancellation_timeline is refund tiers: cancel at least days_out days before arrival to get refund_percentage back. The hotel Q&A comes back as two lists: questions is what has been asked of this hotel and counts against the ask cap, and answers is what came back. Each answer restates the question it addresses, which may be one of questions or one of the request's questions_for_hotels — match by text across both to work out what is still outstanding. terms.expiration_date is the day the offer lapses; while it is still ahead, request_proposal_extension is how the user asks for a later decision date. Once expired is true the offer can no longer be booked, but asking for more time still works: request_proposal_extension sends it back to the hotel to be stood up against the date the user wants, and urls.refresh is where they do the same themselves. Nothing reaches them without asking, so never suggest waiting to see whether something turns up. Booking is not available through these tools — share urls.book to hand the user off to the checkout page, or urls.self for the full terms in the app. An offer that has already been booked carries trip_id and urls.trip instead: it is now a trip, managed with get_trip and the trip tools. The request page opens a hotel and its offer interchangeably: where hotel_url is present it is this hotel there, so share it when the question is about the hotel rather than the quote.
get_request
ChatGPTGet full details for one of the current user's room block requests by id (from list_my_requests): the hotels being sourced, rooms, event spaces, food & beverage, the questions asked of the hotels, and the colleagues who can work on it. hotels names every hotel on the request and links each one — share a hotel's url whenever you name it. That list is populated from the moment the request is submitted, so use it rather than list_request_proposals when no hotel has replied yet; go to list_request_proposals for the offers themselves. This is the sourcing view, and booking does not end it: one request can book more than one hotel, so its remaining hotels go on quoting and can still be worked with. What booking does close is the request itself — rooms, dates, hotel set, and questions_for_hotels are locked from the first booking on, since the offer already booked was quoted against them. trips lists what this request has booked so far; guests, rooms, and agenda for those live in the trip tools.
get_trip
ChatGPTGet full details for one of the current user's trips by id (from list_my_trips): hotel, dates, settings (guest requests, self-paid nights), trip-page configuration, and the colleagues who can plan it. The booked hotel comes back with hotel_id, which get_hotel takes; urls.room_block is its page in the app.
grant_request_planner_access
ChatGPTGrant colleagues planner access to one of the current user's sourcing requests: they can then read every hotel's offer on it, change what's being asked for, and book it. A sourcing request has no guests — nobody attends it — so this is never how someone is added to a trip. Once a request is booked, the trip it produced has its own separate guest list (add_trip_guests) and its own planner access (grant_trip_planner_access); granting access here grants nothing on that trip. get_request already lists who can work on a request, so call this to change that list, not to read it. Everyone already on it keeps their access — this only adds. Any address can be named — a colleague already on the org, or someone who has never heard of Workgrounds. They join the org the first time they sign in. Each newly added planner is emailed to tell them they now have access. Addresses that already have access are skipped silently and returned in skipped_emails; only bring up skipping when that list is present. Removing a planner's access is not available through these tools — hand over the app link for that.
grant_trip_planner_access
ChatGPTGrant colleagues planner access to one of the current user's trips: they can then see and change everything on it — the whole guest list and its notes, the booked rooms, and what the trip costs. This does NOT add anyone to the trip as a guest: it books them no room, puts them on no rooming list, and sends them no invitation. They are helping run the trip, not attending it. Only use this when the user is clearly asking to share the trip with a colleague or let someone help plan it. A plain "add these people to the trip" means guests — that is add_trip_guests. If it could be read either way, ask the user which they mean rather than guessing; granting access shows a colleague the whole guest list and cannot be taken back through these tools. get_trip already lists who can plan a trip, so call this to change that list, not to read it. Everyone already on it keeps their access — this only adds. Any address can be named — a colleague already on the org, or someone who has never heard of Workgrounds. They join the org the first time they sign in. Each newly added planner is emailed to tell them they now have access. Addresses that already have access are skipped silently and returned in skipped_emails; only bring up skipping when that list is present. Removing a planner's access is not available through these tools — hand over the app link for that.
hide_proposal
ChatGPTHide one of the current user's hotel offers, with a reason. Reversible — the user can unhide it from urls.request. Use list_request_proposals to find the proposal id. A booked offer (booked=true) cannot be hidden.
invite_org_planners
ChatGPTInvite colleagues onto the current user's org, so they can plan trips and source hotels for it. This emails each of them an invitation to join. The user may call the org their company, their team, or their enterprise — those all mean the org. Any planner on the org can invite, admin or not. Invitees join as ordinary planners, never as admins — promoting someone is done in the app. An invitation puts a colleague on the org before there's a trip to add them to; if the aim is to let someone work on a particular trip or request, grant_trip_planner_access and grant_request_planner_access take any address directly. Being invited to the org grants no access to any specific trip or request — name them with grant_trip_planner_access or grant_request_planner_access for that. Addresses already on the org are skipped silently and returned in skipped_emails; only bring up skipping when that list is present. An address that was deactivated comes back in deactivated_emails instead, and that one is worth raising: no invitation reaches them and they can't be given a trip or request either until an admin reactivates them in the app. Confirm the addresses with the user before calling this — an invitation email cannot be unsent. A planner who comes back carrying invite_url has no account and no single sign-on to make one for them: that link is the only way they can accept, so pass it on to the user so they can send it if the email doesn't land.
invite_trip_guests
ChatGPTEmail the trip invitation to named guests on one of the current user's trips — the same email the app's invite-guests page sends, with the same message from the planner. Set is_reminder to nudge guests who were invited and have not claimed a room yet, which sends the reminder wording instead. Takes two calls, and the first one sends nothing. Call it without confirm_token and you get back preview: every guest who would be emailed by name and address, the planner's message they would see, which of them are being invited to claim a room and which room that is, and who among them has been invited before. Read that out to the user — the guests by name, not as a count — and get an explicit yes. Then call again with the same arguments plus the preview's confirm_token, and the emails go. This cannot be taken back: these are real people and the email is in their inbox the moment it is sent. So there is no way to invite everyone implicitly — name every guest_id you mean, from list_trip_guests, and let the preview be the readback. custom_message defaults to what the planner last saved on the trip, and sending saves it again, so pass it only when the user gave you the words. A guest with no email address on file cannot be invited, and nothing can be sent at all until the hotel stay is confirmed. Guests who need a room and have none are invited to claim one; where the free rooms will not cover them, this refuses and the invitation has to be sent from urls.invite_guests, where the planner picks the rooms themselves. To give a guest their room rather than let them pick it, name it in assign_rooms: the preview then reads out the room type and dates each of them gets, and the one yes covers both the rooms and the emails. Assigning without inviting anyone is assign_trip_rooms.
list_my_invitations
ChatGPTList the trips the current user has been invited to as a guest, as opposed to the ones they plan (list_my_trips); needs no arguments. Each one comes back with the hotel, the trip's dates, the guest's own check-in date once they have a room, and a url to their trip page. Defaults to trips that haven't ended yet, soonest first; use when=past for trips already over (most recent first) or when=all for both in date order. Returns one page; use limit and offset to page through total. Pass a trip's id to get_my_invitation for the hotel, the schedule and the guest's own reservation.
list_my_requests
ChatGPTList the current user's own room block requests, newest first — this is the right tool for "my requests" and needs no arguments. A request is the sourcing stage: hotels are asked to quote, and each offer the user books becomes a trip, managed with list_my_trips and the trip tools. The booked flag means at least one hotel has been booked — not that the request is finished, since one request can book several hotels and keeps sourcing the rest. Defaults to upcoming requests (one with no room block dates yet counts as upcoming); use when=past or when=all to include requests whose stay is over, and include_archived to include archived ones. Returns one page; use limit and offset to page through total. scope=org widens the list to every planner's requests at the user's org, and is available only to org admins. Use it when the user asks for their org's, their company's, their team's, or a colleague's requests — otherwise leave it alone and don't bring the option up, since for most users it returns nothing they didn't already see. On an org-wide list each request carries a mine flag to separate the user's own from colleagues'; the result's scope reports which scope was actually served.
list_my_trips
ChatGPTList the current user's own booked trips (events at a hotel with a room block) — this is the right tool for "my trips" and needs no arguments. Trips the user attends as a guest are list_my_invitations. A trip is what a room block request becomes once it's booked — use these tools to manage guests, the agenda, and settings after booking. For room block requests that are still being sourced (before they become booked trips), use list_my_requests instead. Defaults to upcoming trips, soonest first; use when=past or when=all to see finished trips, starts_after/starts_before to bound by date, and sort to flip the order. Returns one page; use limit and offset to page through total. scope=org widens the list to every planner's trips at the user's org, and is available only to org admins. Use it when the user asks for their org's, their company's, their team's, or a colleague's trips — otherwise leave it alone and don't bring the option up, since for most users it returns nothing they didn't already see. On an org-wide list each trip carries a mine flag to separate the user's own from colleagues'; the result's scope reports which scope was actually served.
list_request_proposals
ChatGPTList every hotel sourced for one of the current user's requests and where each one stands: quoted (proposal_id present), come back unavailable (available=false), or still to answer (awaiting_quote=true, which covers both a request just sent and a lapsed offer sent back for a fresh quote). proposal_id is present whenever the hotel has responded with a proposal and omitted otherwise. Every quoted offer carries what it costs and what it commits to — room_block_total, booking_total where it has extras, its attrition rate and the minimum that rate owes, and the day it lapses — all formatted for quoting as they stand, so comparing the offers on a request takes this call alone. An offer whose totals_unavailable is true is one whose money could not be worked out: leave it out of any comparison rather than reading its missing totals as a cheaper quote. Use get_proposal for one offer's full terms: room types and rates, fees, taxes, cancellation policy, event space, F&B, and the hotel Q&A. An offer with expired=true has run past its own deadline: it cannot be booked, and it carries refresh_url instead of book_url because it takes the hotel to stand it up again — request_proposal_extension is how the user asks for that, and refresh_url is where they do it themselves. Never tell them to wait for a new proposal to arrive by itself. Booking happens in the app — share an offer's book_url for its checkout page, its url for the full terms, or urls.request to compare them side by side. The request page opens a hotel and its offer interchangeably, so where an offer carries hotel_url, share that when the user is asking about the hotel and url when they're asking about the quote.
list_trip_agenda
ChatGPTList the agenda (itinerary) events for one of the current user's trips, e.g. welcome dinners, sessions, and activities shown to guests on the trip page. Returns one page (see total); use limit and offset to page through longer agendas.
list_trip_guests
ChatGPTList the guests on one of the current user's trips: name, guest-provided name, email, tag, room needs, invitation status, and room_status (assigned/no_room_needed/no_response/not_assigned). Free-text notes are never returned — has_planner_note/has_guest_note only flag that a note exists; open the guest list in the app to read it. Segment with the filters — search (name/email), tag, invited, needs_a_room, room_status, allowed_room_kind — instead of pulling everyone and filtering yourself (e.g. room_status=no_response for "who hasn't RSVP'd", needs_a_room=true + room_status=not_assigned for "who still needs a room"). total reflects the filter; page the matches with limit and offset. The guest ids this returns are what invite_trip_guests takes to email them their invitation or a reminder.
list_trip_room_changes
ChatGPTThe change history (a.k.a. transaction history) for a trip's room block: every change since it was booked — rooms added, date changes (extensions/shortenings), and cancellations — each with when it was applied, whether the guest or planner initiated it, and the cost. Use this for "transaction history", "change history", "what's changed on this trip", "room changes", or "what were we charged for changes". Guests' self-paid personal-night changes aren't included. Read-only. Returns one page (see total); use limit and offset to page through the history, most recent first.
list_trip_rooms
ChatGPTList the rooms in one of the current user's trip room blocks, one entry per room: its dates, assigned guest, status, hotel confirmation number, and whether the guest is self-paying some nights. Narrow with the filters — guest, room_name, status, assigned, hotel_pending, has_self_paid_nights, check_in, check_out — instead of pulling the whole block and filtering yourself. Block-level totals (rooms_total, rooms_unassigned) live on get_trip. Returns one page; total reflects the filters — page it with limit and offset. For the guest list use list_trip_guests, and for the guest change/cancellation requests waiting on you use get_guest_room_requests.
remove_trip_agenda_event
ChatGPTDelete an agenda event from one of the current user's trips. Reversible by adding it again. Use list_trip_agenda to find the event id.
remove_trip_guests
ChatGPTRemove one or more guests from one of the current user's trips. Deletes them from the guest list and unassigns any room they held; the guests are not notified. This is permanent: the guest's record is deleted outright, including any notes on them, and not even Workgrounds can restore it. Name the guests you are about to remove and confirm with the user before calling it. Two kinds of guest cannot be removed here and must be handled in the app: guests self-paying for some of their nights (they must give up those nights first), and guests who have already been invited and have a room assigned (removing them isn't reversible without re-inviting them). If any requested guest is in either state, the whole request is rejected and none are removed. Use list_trip_guests to find the guest ids.
request_proposal_extension
ChatGPTAsk for more time to decide on one of the current user's offers. This is the route for anything of the form "can I have until the 20th", "can they hold this longer", "I need another week" — never ask_proposal_question, which reaches the hotel as an ordinary question and moves no deadline. It works whether or not the offer has already expired; what differs is only what the user sees while the hotel makes up its mind, which the outcome in the result names. On an offer still standing (expired=false), nothing about it changes: the wanted date goes in front of the Workgrounds team, who take it to the hotel. On one that has already expired (expired=true), it goes back to that hotel to be stood up against the wanted date, so its terms come off the request until they answer, and what they come back with may be priced differently. The hotel decides either way, so never tell the user the date is theirs yet. Either way a date given has to fall at least 7 days before the first night of the block, and a booked offer can't be changed at all. Where the block starts sooner than that, no date can be promised — on an expired offer, call again with no decision_date to send it back to the hotel regardless, and tell the user their decision date can't be carried. On an expired offer this is destructive in one way worth naming: its terms come off the request while the hotel answers, so confirm first if the user may still want to read them. Calling it again replaces the date that was asked for. Use list_request_proposals to find the proposal id.
set_request_rooming_list
ChatGPTPut guest names against the rooms of one of the current user's requests, so they carry into the trip when a hotel is booked. Replaces the whole list: names not in this call are cleared, and [] clears it entirely. This does NOT change what the hotels are asked — they never see guest names, so every offer stays bookable and nobody is asked to quote again. Changing what is being asked for is update_request. Takes two calls, and the first one writes nothing. Call it without confirm_token and you get back preview: every room in the block and who lands in it. Read that out to the user and get an explicit yes, then call again with the same arguments plus the preview's confirm_token. A guest with check_in and check_out takes that exact room; a guest without takes the next room still free, so a list of plain names fills the block in order. Naming more guests than the block has rooms fails — change the block with update_request first.
update_request
ChatGPTChange one of the current user's requests in a single step: what it asks for (room block, alternative dates, event spaces, food & beverage, questions for the hotels, how much of it an offer has to cover) and which hotels hear about it - hotels to ask again, to add and to remove. No proposal is lost. When what the request asks for changes, the hotels it goes to quote again against the new terms, and each one's current offer stays readable but can no longer be booked. The rest keep their current proposals - the user can still book those as-is. A hotel still owing a proposal always gets a changed request. Takes two calls, and the first one changes nothing. Call it without confirm_token and you get back preview: the request as it would be, which hotels are re-asked, added, removed and left untouched, and offers_superseded naming the offers that stop being bookable. Read that preview out to the user and get an explicit yes. Then call again with the same arguments plus the preview's confirm_token. Read the preview's advisories out before taking their yes. Trimming rooms is the common one: an offer in hand can be booked for fewer rooms at checkout, so the change request was never needed. A confirmed call returns updated: the request as it now stands, with a urls object - share urls.self so the user can watch the new quotes come in. Once the request has booked a hotel (booked=true) what it asks for is locked, and only add_hotel_ids is accepted, which is how a booked request keeps sourcing. A request holds at most 10 hotels, not counting removed ones.
update_trip
ChatGPTUpdate settings on one of the current user's trips. Only the fields you provide are changed; omit a field to leave it unchanged. Does not notify guests. Returns the trip's full details, like get_trip.
update_trip_agenda_event
ChatGPTUpdate an existing agenda event on one of the current user's trips. Replaces the event's fields with the supplied values. Use list_trip_agenda to find the event id.
update_trip_guest
ChatGPTUpdate a guest's details on one of the current user's trips: name, email, tag, and whether they need a room. Only the fields you provide are changed; everything else (invitations, room assignment) is left untouched. Does not notify the guest. Use list_trip_guests to find the guest id.
add_trip_agenda_event
Claudeadd_trip_guests
Claudearchive_request
Claudeask_proposal_question
Claudeassign_trip_rooms
Claudecreate_request
Claudefind_hotels
Claudeget_guest_room_requests
Claudeget_hotel
Claudeget_my_invitation
Claudeget_my_profile
Claudeget_org_offices
Claudeget_org_planners
Claudeget_proposal
Claudeget_request
Claudeget_trip
Claudegrant_request_planner_access
Claudegrant_trip_planner_access
Claudehide_proposal
Claudeinvite_org_planners
Claudeinvite_trip_guests
Claudelist_my_invitations
Claudelist_my_requests
Claudelist_my_trips
Claudelist_request_proposals
Claudelist_trip_agenda
Claudelist_trip_guests
Claudelist_trip_room_changes
Claudelist_trip_rooms
Clauderemove_trip_agenda_event
Clauderemove_trip_guests
Clauderequest_proposal_extension
Claudeset_request_rooming_list
Claudeupdate_request
Claudeupdate_trip
Claudeupdate_trip_agenda_event
Claudeupdate_trip_guest
Claude