Guesty Reservations-V3 & Folio Migration

    1

    Migrate off Guesty's retiring legacy reservations endpoints before March 1, 2027 — the endpoint map, the folio money pull, and the verification procedure that proves your new numbers match to the cent.

    $19

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Guesty Reservations-V3 & Folio Migration

    Example session with this skill installed

    Show me how to map the legacy money.fareAccommodation and money.commission fields to the new folio API and how to avoid the stale commission trap.

    • Read your context and instructions
    • Compiled the guesty reservations-v3

    I have mapped the legacy financial fields to the Guest-Folio V3 equivalents and included the logic to avoid the list-view commission discrepancy.

    Guesty Folio Mapping and Commission Logic

    To replicate the legacy money object accurately, you must pull data from GET /v1/guest-folio/overview using batching. The critical fix for the commission trap is to never reconcile against the legacy

    list endpoint, as its values are often stale.

    Legacy FieldFolio V3 FieldReconciliation Rule
    money.fareAccommodationrawAccommodationFareShould match to the cent.
    money.commissioncommissionMatch against legacy DETAIL view only.
    money.hostPayouthostPayoutDirect equivalent.
    money.netIncomenetIncomeDirect equivalent.

    Implementation: Folio Batch Pull

    
    # Constants for the Guesty API limits
    FOLIO_BATCH_LIMIT = 200
    
    def get_folio_data(reservation_ids):
        # Map to store verified financial data
        financials = {}
        
        for i in range(0, len(reservation_ids), FOLIO_BATCH_LIMIT):
            batch = reservation_ids[i:i + FOLIO_BATCH_LIMIT]
            # Request specific fields to avoid accommodationFareNet trap
            params = [
                ("reservationIds[]", rid) for rid in batch
            ] + [
                ("fields[]", "rawAccommodationFare"),
                ("fields[]", "commission"),
                ("fields[]", "hostPayout"),
                ("fields[]", "netIncome")
            ]
            
            response = guesty_client.get("/v1/guest-folio/overview", params=params)
            for record in response.get("results", []):
                financials[record["reservationId"]] = record
                
        return financials
    

    Next steps

    1. Identify all legacy scripts using money.commission from the list view.
    2. Run a Stage 1 sample verification across one reservation per channel (Airbnb, Vrbo, Direct).
    3. Verify the base URL is set to https://open-api.guesty.com to prevent timeouts.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Guesty's legacy reservations endpoints retire on March 1, 2027 — the reservations list and detail, the payments sub-resource, and the guest payment-methods endpoint all go away, and every owner report, portfolio sweep, and reconciliation built on them goes with them. This pack is the complete migration method, documented from a production cutover. You get the full endpoint map (legacy → reservations-v3 search and guest-folio), including the replacements that aren't one-to-one: there is no single-reservation GET on v3, and charging a guest becomes a two-step create-then-pay. You get the search endpoint's real behavior — limit/skip paging with hasMore, a full-history, all-statuses scope with no "upcoming" default — and its most expensive gotcha: no server-side filter can be trusted. The status parameter looks like it works on a small probe and is silently ignored on a full pull; the date parameters are ignored too. The pack gives you the local-filtering patterns and the recipe for replicating the legacy upcoming scope. Then the money: how to pull reservation money from the guest-folio API with array parameters in batches of up to 200 IDs, the exact field set that reproduces the legacy money object, and the two field traps — accommodationFareNet is not the fare, and totalFees is not the cleaning fee. The centerpiece is the stale-commission trap: the legacy LIST endpoint's commission figure is stale on many records and under-reports, sometimes by hundreds of dollars per reservation, while the legacy DETAIL value and the folio value agree to the cent. Verify against the wrong view and you'll chase a phantom discrepancy or abandon a correct migration; the pack explains which source is authoritative and why. Finally, the two-stage verification-to-the-cent procedure — a cross-channel sample check, then a full-scope batch reconciliation with set identity, a $0.00 fare delta, and every differing row named — plus the migration checklist and the cutover verification steps that keep the legacy pull from surviving inside your scheduled jobs. Built for anyone whose Guesty reporting has a hard deadline it didn't choose.

    Server-side filters for status and dates on V3 search are unreliable and require local filtering. The new two-step payment flow requires live validation of field names.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed today

    Permissions

    No special permissions declared or detected

    Listedtoday

    What's inside

    Frequently Asked Questions

    This skill provides a structured migration path to transition from Guesty's legacy /v1/reservations to the V3 and Guest-Folio APIs, specifically addressing the 2027 retirement deadline and preventing common data corruption issues.

    You will receive an implementation roadmap, endpoint mapping documentation, pagination logic, and a two-stage reconciliation workflow to ensure financial data remains accurate down to the cent.

    Unlike generic AI, this skill includes documentation on documented API quirks, such as the 'stale commission' trap and unreliable server-side filters that often lead to silent data corruption during manual migrations.

    The skill is designed for developers or teams using Python and standard REST clients who need to rebuild reporting, owner statements, or payout reconciliation tools.

    The skill accounts for the current unreliability of V3 server-side filters by providing logic for local status and date filtering to ensure your reservation views remain consistent with legacy 'upcoming' scopes.

    New in Business & Operations