​

RollingGo Hotel MCP Upgrade Guide: H5 to Mini Program — Multi-Option Guide

Applicable Version: v2.5
Updated: 2026-08-14
Applicable To: Existing channels/partners currently using the H5 solution (bookingUrl) and planning to upgrade to a Mini Program landing experience.

​

1. Background

​

2. Options Overview and Comparison

​

3. Option A: H5_TO_MINIAPP (H5 to Mini Program)

​

3.1 Use Cases

​

3.2 Integration Details

• The API returns a WeChat encrypted link (https://wxmpurl.cn/*). When users click the link inside WeChat, the RollingGo booking Mini Program is automatically launched without requiring users to search for it manually.
• Link generation and maintenance are handled by RollingGo. The frontend can use the link directly.

​

3.3 API Response Example

{
  "success": true,
  "hotelId": 102906,
  "checkIn": "2026-08-12",
  "checkOut": "2026-08-13",
  "miniProgramInfo": {
    "type": "H5_TO_MINIAPP",
    "url": "https://wxmpurl.cn/abCDef123456"
  },
  "roomRatePlans": [ ... ],
  "message": "Search successful"
}

​

3.4 Migration Steps

1. Contact RollingGo to configure the channel landing type as H5_TO_MINIAPP.
2. Update the frontend to read the miniProgramInfo field.
3. Expose the url as a regular link/button to users. It must be triggered by a user click/tap, after which WeChat will automatically launch the Mini Program.

​

3.5 Code Example

if (resp.miniProgramInfo && resp.miniProgramInfo.type === "H5_TO_MINIAPP") {
  const url = resp.miniProgramInfo.url;   // https://wxmpurl.cn/abCDef123456
  // H5 page: use it directly as a link
  // Book Now
}

​

3.6 Notes

• ⚠️ web-view limitation: A Mini Program’s web-view cannot navigate to a Mini Program through a URL Link. For this scenario, use Option C (MINIAPP_TO_MINIAPP).

​

4. Option B: APP_TO_MINIAPP (App to Mini Program)

​

4.1 Use Cases

​

4.2 Integration Details

• The API returns a WeChat Scheme link (weixin://dl/business/?...), which can directly launch the Mini Program on both iOS and Android.

​

4.3 API Response Example

{
  "success": true,
  "hotelId": 102906,
  "checkIn": "2026-08-12",
  "checkOut": "2026-08-13",
  "miniProgramInfo": {
    "type": "APP_TO_MINIAPP",
    "url": "weixin://dl/business/?appid=wx_SAMPLE_APP_ID&path=pages/hotel/detail/index&query=id%3D102906%26checkInDate%3D2026-08-12%26checkOutDate%3D2026-08-13%26roomCount%3D1%26adultCount%3D1%26childCount%3D0%26childAgeDetails%3D%26utm_source%3DfusionAI-2026"
  },
  "roomRatePlans": [ ... ],
  "message": "Search successful"
}

​

4.4 Migration Steps

1. Contact RollingGo to configure the channel landing type as APP_TO_MINIAPP (RollingGo handles the remaining WeChat-side configuration).
2. Read miniProgramInfo.url on the frontend.
3. Directly invoke the system to open the Scheme and launch the Mini Program.

​

4.5 Code Example

// Directly open the Scheme to launch the WeChat Mini Program
window.location.href = resp.miniProgramInfo.url;

​

4.6 Notes

• WeChat-side configuration is handled by RollingGo. If the Mini Program fails to launch, contact RollingGo for troubleshooting.

​

5. Option C: MINIAPP_TO_MINIAPP (Mini Program to Mini Program) ★ Recommended for Mini Program Scenarios

​

5.1 Use Cases

​

5.2 Integration Details

• The API returns structured parameters: appId (RollingGo Mini Program AppID) + path (page path) + query (query string).
• The frontend calls wx.navigateToMiniProgram to initiate the navigation, using the path?query format.

​

5.3 API Response Example

{
  "success": true,
  "hotelId": 102906,
  "checkIn": "2026-08-12",
  "checkOut": "2026-08-13",
  "miniProgramInfo": {
    "type": "MINIAPP_TO_MINIAPP",
    "appId": "wx_SAMPLE_APP_ID",
    "path": "pages/hotel/detail/index",
    "query": "id=102906&checkInDate=2026-08-12&checkOutDate=2026-08-13&roomCount=1&adultCount=1&childCount=0&childAgeDetails=&utm_source=fusionAI-2026"
  },
  "roomRatePlans": [ ... ],
  "message": "Search successful"
}

​

5.4 Migration Steps

1. Contact RollingGo to configure the channel landing type as MINIAPP_TO_MINIAPP.
2. Read miniProgramInfo on the frontend and store the navigation parameters.
3. Bind the navigation to a user click event and call wx.navigateToMiniProgram (must be triggered by a user click; do not call it directly inside an API callback).
4. (Optional) Return to your Mini Program after booking and handle the return parameters in onShow.

​

5.5 Code Example

// User clicks the "Book Now" button
onBookingTap() {
  const { appId, path, query } = this.miniProgramInfo;
  wx.navigateToMiniProgram({
    appId,
    path: query ? `${path}?${query}` : path,
    extraData: {},
    success() { /* Navigation successful */ },
    fail(err) { wx.showToast({ title: "Failed to launch booking Mini Program. Please try again.", icon: "none" }); }
  });
}

​

5.6 Notes

• path is the page path. All dynamic parameters are contained in query. Do not split or truncate them.
• If the Mini Program fails to launch, the API does not provide an automatic fallback. The channel is responsible for displaying guidance to the user.
• WeChat may display a confirmation dialog before navigation. This is standard platform behavior.

​

6. Option Selection Guide

[Where is the user entering from?]
   │
   ├─ Inside a Mini Program (web-view or native page) ──► Option C: MINIAPP_TO_MINIAPP (Recommended)
   │
   ├─ Host App ─────────────────────────────────────────► Option B: APP_TO_MINIAPP (Direct launch)
   │
   └─ Browser / H5 / Official Account webpage ─────────► Option A: H5_TO_MINIAPP (Auto-launch in WeChat)

​

7. General Notes (Applicable to All Three Options)

1. Mutual Exclusivity: After the upgrade, the response returns miniProgramInfo instead of bookingUrl. The two fields will never appear at the same time.
2. Parameter Integrity: Fully pass through id / checkInDate / checkOutDate / roomCount / adultCount / childCount / childAgeDetails. Do not manually modify the parameter values.
3. No Automatic Fallback: If the Mini Program fails to launch, there is no automatic fallback to H5. The channel is responsible for displaying guidance to users.
4. No Changes to Request Parameters: Existing API request parameters and invocation methods remain unchanged. Only the landing-related response fields are added.

​

8. Acceptance Checklist

​

9. FAQ