Ananas GDS is the B2B data distribution layer for the tourism industry. Connect hotels, tour operators, and travel agents through a single platform that handles fact sheets, stop sales, allotments, photos, and surveys — no email chains, no manual PDFs, no guesswork.
Explore the Docs
Browse by topic — from initial setup and authentication through to API integration and billing.
Register your account, create properties, and connect your first partner in under 15 minutes.
→Session-based login, API token management, sub-user roles, and access control security model.
→Property data distribution across 12+ fact categories — from general info to room types and facilities.
→Availability calendar, allotment management, event states, and real-time partner notifications.
→Contract lifecycle, connection management, data-sharing permissions, and the partner marketplace.
→TO dashboard, hotel and room name mapping, override facts, and consuming partner data via API.
→B2B invoice creation, line items, status lifecycle, and PDF export for accommodation and TO accounts.
→Stripe subscriptions, available plans, billing cycles, feature access, and webhook events.
→API tokens, per-token analytics, usage statistics, webhook integrations, and the API explorer.
→For Accommodation Providers
Accommodation providers use Ananas GDS to publish structured property data to their entire tour operator network from a single control point — eliminating manual PDF updates, outdated Excel sheets, and repetitive email requests.
Manage property data across 12+ categories: general info, location, facilities, room types, board types, services, policies, contacts, and more. Publish once, distribute everywhere.
Upload high-resolution photos, organise into categories, and publish a gallery that tour operators can access directly via API or download as a structured photo set.
Block dates, set allotment limits, and manage room-level availability in a calendar interface. Changes push immediately to all connected partners via the API.
Connect with tour operators through contract-based partnerships. Define exactly which properties and data categories each partner can access before distributing anything.
Issue and track invoices directly through the platform. Maintain a clear financial record with your distribution partners without leaving the dashboard.
Invite team members — Front Office, Revenue Manager, PR — and assign granular permissions per role and per property. Full audit trail of all changes.
For Tour Operators & Travel Agents
Tour operators connect to accommodation partners through Ananas GDS and consume live, structured data via API — no more waiting for updated PDFs, chasing property contacts, or reconciling mismatched room names in spreadsheets.
Pull partner hotel data via authenticated API tokens. Facts, photos, stop sale, and surveys all available as structured JSON — ready to feed directly into your booking engine or CMS.
Map hotel names, room types, and board codes to your internal catalogue identifiers. Maintain a clean translation layer between partner naming conventions and your own system.
Override specific fact sheet fields for your own catalogue without affecting the source data at the hotel. Your overrides are stored per-partner and returned only on your API calls.
Receive real-time availability and stop sale data for connected properties. Query per property, per date range, or consume webhook events as calendar state changes.
For Developers
The Ananas GDS REST API uses token-based authentication. Every API call is scoped to a specific partner token, giving you access only to the data that has been explicitly shared with you through an active partner contract.
Note
API tokens are created and managed in the Developer Tools section of your dashboard. Each token is linked to a specific partner contract and can be revoked at any time without affecting other tokens.
Fetch a hotel fact sheet using your partner API token:
GET /api/v1/facts/{token}/
Authorization: Token <your-api-token>
Accept: application/jsonA successful response returns a structured JSON object containing all published fact sheet sections for the property the token is scoped to:
{
"property": {
"name": "Grand Hotel Palermo",
"type": "Hotel",
"country": "IT",
"city": "Palermo",
"stars": 5
},
"general": { ... },
"rooms": [ ... ],
"facilities": { ... },
"stop_sale": {
"status": "open",
"blocked_dates": []
}
}Available Endpoints
| Method | Endpoint | Description | Status |
|---|---|---|---|
| GET | /api/v1/facts/{token}/ |
Full fact sheet for a property | Active |
| GET | /api/v1/photos/{token}/ |
Photo gallery with CDN URLs | Active |
| GET | /api/v1/stopsale/{token}/ |
Availability calendar and allotments | Active |
| GET | /api/v1/surveys/{token}/ |
Survey responses for a property | Active |
| GET | /api/v1/contracts/ |
List active partner contracts | Active |
| GET | /api/v1/invoices/ |
B2B invoice list and detail | Beta |
Platform Architecture
Understanding the stack helps when debugging integrations or building on top of the API.
Test Environment
A staging environment is available at testingarea.hotelfacts.net. Use it to validate API integrations before pointing your system at the production instance at app.ananas-gds.com.