> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rollinggo.store/llms.txt
> Use this file to discover all available pages before exploring further.

# RollingGo REST API Reference: Travel MCP Endpoints

> An overview of RollingGo's REST API for travel search and booking, including base URLs, authentication, response format, and rate limits.

RollingGo provides a REST API — and an MCP-compatible interface — for programmatic access to travel search, booking, and management. This reference covers all endpoints available to **Enterprise** and **Developer** partners. Personal users authenticate via OAuth and do not use API Keys.

## Base URLs

Use the base URL that matches the region where your requests originate. All endpoints listed in this reference are appended to the appropriate base URL.

| Region | Base URL |
| - | - |
| International / HK / Macau / Taiwan | `https://api.rollinggo.ai/v1` |
| China Mainland | `https://api.rollinggo.cn/v1` |

## Request Format

Every request to the RollingGo API must meet the following requirements:

* Set `Content-Type: application/json` on all requests.
* Set `Authorization: Bearer YOUR_API_KEY` on all requests. See [Authentication](/api/authentication) for details.
* Send request bodies as JSON.

## Response Format

All API responses are returned as JSON. Use the top-level `status` field to determine whether a request succeeded or failed.

**Successful responses** include `status: "ok"` alongside a `data` object and a `requestId` you can use when contacting support:

```json theme={null}
{
  "status": "ok",
  "data": { ... },
  "requestId": "req_abc123"
}
```

**Error responses** include `status: "error"`, a machine-readable `code`, a human-readable `message`, and a `requestId`:

```json theme={null}
{
  "status": "error",
  "code": "unauthorized",
  "message": "Invalid or missing API Key",
  "requestId": "req_def456"
}
```

## Rate Limits

Your rate limits depend on your partner plan. You can view your current limits at any time in your **Partner Center dashboard** under **Settings → API Usage**.

Every API response includes the following headers so you can track your consumption in real time:

| Header | Description |
| - | - |
| `X-RateLimit-Limit` | Total requests allowed per minute |
| `X-RateLimit-Remaining` | Requests remaining in the current window |
| `X-RateLimit-Reset` | Unix timestamp when the current window resets |

<Warning>
  When you exceed your rate limit, the API returns HTTP **429 Too Many Requests** with a `Retry-After` header indicating how many seconds to wait before retrying.
</Warning>

## Available Endpoints

The table below lists every endpoint covered in this reference. Click any endpoint path to jump to its full documentation.

| Endpoint | Method | Description |
| - | - | - |
| `/travel/search` | `POST` | Search for flights, hotels, or packages |
| `/travel/book` | `POST` | Initiate a booking for a selected result |
| `/travel/booking/{id}` | `GET` | Retrieve details for an existing booking |
| `/webhooks/register` | `POST` | Register a webhook endpoint |
| `/webhooks/{id}` | `DELETE` | Remove a webhook registration |

## Next Steps

<CardGroup cols={2}>
  <Card title="Authentication" icon="key" href="/api/authentication">
    Learn how to authenticate your requests with your API Key.
  </Card>

  <Card title="Travel Search" icon="magnifying-glass" href="/api/travel-search">
    Search for flights, hotels, and travel packages.
  </Card>

  <Card title="Booking" icon="calendar-check" href="/api/booking">
    Initiate and manage bookings programmatically.
  </Card>

  <Card title="Webhooks" icon="webhook" href="/api/webhooks">
    Register webhook endpoints to receive real-time events.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.