Turn Agoda YCS into an API

What you can build on YCS

• Get reservations

  Build this

  Reads Bookings >> Reservations for one property and stay dates, on the All, Confirmed, Amended or Cancelled tab, and opens each booking for its details.

  Takes

  Property, stay dates, tab (optional)

  Returns

  Booking ID, status, guest name, stay dates, room type, rate plan, payment model

• Get bookings ready for payout

  Build this

  Reads Finance > Payouts for one property: the bookings listed under Bookings ready for payout and the entries in the Adjustments section.

  Takes

  Property

  Returns

  Booking ID, amount, adjustments

• Get past payouts

  Build this

  Reads Finance > Past payouts for one property: each payout batch with its bookings, amount and Value Date.

  Takes

  Property, since date (optional)

  Returns

  Payout batch, Value Date, bookings, amount

• Update availability and rates on the Calendar

  Build this

  Opens Rates and availability >> Calendar, sets Availability per day for a room type and the rate for a rate plan on the dates you give, then saves.

  Takes

  Property, room type, rate plan, dates, availability per day, rate

  Returns

  Room type, rate plan, dates, availability per day, rate, saved

Automate YCS with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

• Amended and cancelled reservations, every property

  Build this

  Starts

  Every day at 7:00

  Step 1

  For each property you name, get the reservations on the Amended and Cancelled tabs for stays in the next 30 days.

  Step 2

  Keep the bookings that were not on those tabs on the last run.

  Step 3

  Email you the list, one section per property.

• Bookings ready for payout, for finance to confirm

  Build this

  Starts

  Every Monday at 8:00

  Step 1

  For each property, get the bookings listed under Bookings ready for payout and the Adjustments.

  Step 2

  Stop when no property has a booking ready.

  Step 3

  Email you each property's bookings and adjustments, so someone confirms the payout in YCS.

• Past payouts, posted to your accounting system

  Build this

  Starts

  Every weekday at 9:00

  Step 1

  For each property, get the past payouts.

  Step 2

  Keep the payout batches that were not there on the last run.

  Step 3

  Post each batch, with its Value Date, Booking IDs and amount, to your accounting webhook.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get reservations” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "ycs.agoda.com/get_reservations",
    "input": {
      "property": "Northwind Riverside Hotel",
      "stay_from": "2026-11-20",
      "stay_to": "2026-11-30",
      "tab": "Amended"
    }
  }'

{
  "status": "completed",
  "data": {
    "property": "Northwind Riverside Hotel",
    "tab": "Amended",
    "reservations": [
      {
        "booking_id": "880214537",
        "status": "Amended",
        "guest_name": "Dana Whitfield",
        "check_in": "2026-11-22",
        "check_out": "2026-11-25",
        "room_type": "Deluxe Double",
        "rate_plan": "Breakfast included",
        "payment_model": "Agoda Collect (PREPAID)"
      }
    ],
    "count": 1
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

YCS’s own options

Agoda documents the YCS API (Agoda Connectivity API) for rates, availability, restrictions, products and bookings. Agoda says it can be used by properties connected through a channel manager; existing partners ask their Account Manager or the connectivity support team. A property without one works in YCS itself, where the reservation list downloads as CSV.

Read on November 12, 2026: Agoda supply API introduction, How do I use Partner Portal?, Tracking Agoda Special Offers bookings in Reservations.

Signing in to YCS

YCS, which Agoda's help also calls the Partner Portal, asks for your email and password. The first sign-in sends a sign-in link by email, a newly linked username gets a PIN by email or the app, and a session ends after 6 hours idle. With Fous you sign in once through YCS's own sign-in: the login is sealed with AES-256, emailed links and codes are handled, and an expired session is signed back in.

Worth knowing

Channel manager properties update elsewhere

Agoda's help says a property connected to a channel manager updates its price and availability in that system, not in the Calendar. A Calendar method fits a property that manages YCS by hand.

Payouts are not automatic

Bank transfer bookings become payable 30 days after departure, each payout is confirmed by hand with Get Payout and Confirm, and funds arrive in 3 to 5 business days.

Finance depends on how Agoda pays you

The Finance tab appears only for properties paid by Telex Transfer, e-Card or UPC on ePass. A property on another arrangement has no payout pages to read.

One property at a time

A user with several properties picks one under Listings before Reservations, the Calendar or Finance show anything, so a method takes the property as an input.

More in Travel and hospitality

• IATA BSPlink
• My ARC
• Amadeus Selling Platform Connect
• Travelport Smartpoint
• Alloggiati Web
• SES.Hospedajes
• Cvent Supplier Network
• Booking.com Extranet
• Expedia Partner Central
• Trip.com eBooking
• Tripadvisor Management Centre
• Airbnb hosting dashboard
• GetYourGuide Supplier Portal
• Viator Supplier Center

Other industries: AFPnet, KRA iTax, e-Zamówienia, ePortal ESTV, The Compliance Engine, ApplyOnline.