RollingGo OAuth 2.0 Authorization Service Documentation
Welcome to the RollingGo OAuth 2.0 Authorization Service! This document is designed to help third-party developers integrate RollingGo account login into their applications. We support the standard OAuth 2.0 Authorization Code Grant, and recommend that clients (especially public clients such as mobile applications, desktop applications, SPAs, etc.) use the PKCE (Proof Key for Code Exchange) security extension. RollingGo provides two service nodes. The integration process and parameters are exactly the same; only the endpoint domains are different. Please select the appropriate node based on your target users:
MCP Host is the host of the RollingGo MCP (Model Context Protocol) service. It allows AI applications (such as agents and LLM clients) to connect to RollingGo’s hotel capabilities through the standard MCP protocol. The connection URL is https://MCP_HOST/mcp/hotel.
🚀 Authorization Integration Flow
The integration process mainly consists of three steps:- Guide the user to the authorization page and obtain an authorization code (
code). - Receive the redirect and obtain the authorization code (
code). - Exchange the authorization code (
code) for an access token (access_token).
Step 1: Request Authorization
Your application needs to redirect the user to the RollingGo authorization endpoint. Request Method:GET
Request URL:
- Mainland China:
https://api.rollinggo.cn/oauth2/authorize - Overseas & Hong Kong/Macau/Taiwan:
https://api.rollinggo.ai/oauth2/authorize
Step 2: Handle Callback
After the user grants authorization, the browser redirects to yourredirect_uri:
Step 3: Exchange Code for Token
Send a POST request to exchangecode for an access_token:
Request Method: POSTRequest URL:
- Mainland China:
https://api.rollinggo.cn/oauth2/token - Overseas:
https://api.rollinggo.ai/oauth2/token
application/x-www-form-urlencoded
Parameters:
grant_type:authorization_codeclient_id: your application client IDclient_secret: required for Confidential Clients (Web backends)code: authorization code from Step 2redirect_uri: matching Step 1code_verifier: PKCE verifier string

