Skip to main content
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.

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 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:
Error responses include status: "error", a machine-readable code, a human-readable message, and a requestId:

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:
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.

Available Endpoints

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

Next Steps

Authentication

Learn how to authenticate your requests with your API Key.

Travel Search

Search for flights, hotels, and travel packages.

Booking

Initiate and manage bookings programmatically.

Webhooks

Register webhook endpoints to receive real-time events.