Getting Started
Create your account, explore the dashboard, and start distributing hotel data in minutes.
Account Types
Ananas GDS supports two distinct account types. Your account type determines which dashboard you see, which features are available, and how you interact with partners.
| Account Type | Who It Is For | Primary Role |
|---|---|---|
| Accommodation Provider | Hotels, resorts, serviced apartments, hostels | Publish and distribute property data to partners |
| Tour Operator / Travel Agent | Tour operators, OTAs, travel agencies, cruise lines | Consume partner hotel data, configure mappings, access via API |
Accommodation Provider
Hotels and resorts use the accommodation account to manage everything about their properties. This includes:
- Creating and maintaining properties (one account can manage multiple properties)
- Filling in fact sheets across 12+ categories — general info, room types, dining, wellness, transport, and more
- Uploading and organizing property photos
- Setting stop sales and managing allotment calendars
- Issuing API tokens to tour operator partners
- Reviewing partner connection requests and managing contracts
- Inviting team members as sub-users with granular permission flags
Tour Operator / Travel Agent
Tour operators and travel agents use the TO account to access partner hotel data programmatically and configure how that data maps into their own systems:
- Browsing connected partner properties
- Configuring hotel and room mappings (mapping Ananas room types to internal catalogue IDs)
- Applying fact overrides — local edits to partner data without modifying the source
- Managing API tokens for automated data pulls
- Reviewing analytics for API consumption
Registration
All new accounts are created through the registration form at app.ananas-gds.com/register. The form collects:
- Email address — Used as your login identifier. Must be unique across the platform.
- Password — Minimum length enforced. Choose a strong password — no reset email is sent automatically on lockout.
- First and last name — Your personal display name on the account.
- Account type — Select either Accommodation Provider or Tour Operator. This cannot be changed after registration.
- Country — Your country of operation. Used for regional settings and compliance.
- Company name — The organization name associated with your account.
After submitting the form, your account is created with an approval_status of pending. You will not be able to log in until an administrator approves your account.
Manual Approval Required
Accounts require manual approval by an Ananas GDS administrator. You will receive an email notification once your account is approved. This typically takes 1–2 business days. Do not attempt to log in before receiving the approval email.
Approval Statuses
| Status | Meaning | Can Log In |
|---|---|---|
pending |
Registration submitted, awaiting admin review | No |
approved |
Account approved and fully active | Yes |
rejected |
Registration was declined | No |
paused |
Account temporarily suspended by admin | No |
First Login
Once you receive your approval email, navigate to app.ananas-gds.com and click Sign In.
- Enter your email and password — The same credentials you used during registration.
- Remember Me (optional) — Selecting this extends your session inactivity timeout from 30 minutes to 7 days. Useful on personal devices; avoid on shared computers.
- Submit — The platform validates your credentials, checks approval status, and creates your session.
- Dashboard redirect — On success, you are routed to the appropriate dashboard based on your account type (accommodation or tour operator).
Concurrent Session Limit
Each account may have a maximum of 2 active sessions at any given time. If you log in from a third device while two sessions are already active, the login is rejected and a security alert is sent to your account email. To free up a session, log out from one of the active devices or wait for an inactive session to expire.
| Session Type | Inactivity Timeout |
|---|---|
| Standard (Remember Me off) | 30 minutes |
| Extended (Remember Me on) | 7 days |
Dashboard Overview
After login, you land on a role-specific dashboard. The interface adapts entirely to your account type.
Accommodation Dashboard
The accommodation dashboard is organized around your properties. The main areas are:
- Property selector — Switch between multiple properties if your account manages more than one. Each property has its own fact sheets, photos, and stop sale calendar.
- Fact sheet sections — Tabbed interface covering 12+ categories: general info, rooms, dining, wellness, sports, business facilities, transport, accessibility, sustainability, and more.
- Gallery — Upload and manage photos. Photos can be tagged by category and room type, and are served to partners via the API.
- Stop sale calendar — Visual calendar for creating and managing stop sale events and allotment periods.
- Partner connections — Review pending connection requests, manage active partner contracts, control which partners have access to which data.
- Dev Tools — Create and revoke API tokens, view per-token usage analytics, and access the API statistics dashboard.
Tour Operator Dashboard
The tour operator dashboard is focused on consuming and transforming partner hotel data:
- Partner properties list — Browse all hotels and resorts connected to your account via active contracts.
- Mapping configuration — Map Ananas hotel and room identifiers to your internal catalogue IDs so API responses align with your system's schema.
- Override facts — Apply local edits to partner fact data (e.g., update a room description for your catalogue) without modifying the accommodation provider's source data.
- API token management — Generate tokens for your integration systems, view usage statistics, and revoke tokens when needed.
Sub-Users
Account owners can invite team members as sub-users. Sub-users share the same account but operate under a set of permission flags that restrict what they can see and do.
Sub-users are assigned a role (such as General Manager, Reservations, Front Office, Public Relations, or IT) and a set of boolean permission flags:
| Permission Flag | Controls Access To |
|---|---|
properties |
Property management and settings |
facts |
Fact sheet editing |
photos |
Photo gallery management |
stop_sales |
Stop sale calendar and allotments |
company |
Company profile and settings |
contacts_manager |
Contact directory |
partner_connections |
Partner contract management |
publishing_manager |
Publishing and distribution controls |
developer_tools |
API token management and statistics |
Additionally, sub-user access can be scoped to specific properties via region and property access controls — a sub-user managing one hotel in a chain will not see data for other properties unless explicitly granted access.
For full sub-user setup instructions, invitation flow, and permission management, see Admin: Sub-Users.
Next Steps
Now that you have an account and understand the basics, choose the path that matches your role:
Set up your properties, fill in fact sheets, upload photos, and connect to tour operator partners.
Connect to hotel partners, configure mappings, apply overrides, and start consuming data via API.
Full API endpoint reference with request/response formats, authentication, and code examples.
Deep dive into the permission system, role flags, sub-user access controls, and property scoping.