What is an Organization?

An Organization represents a property or business within Recranet Booking. It serves as the top-level container for all data in the system. Every reservation, accommodation, guest, and transaction belongs to exactly one organization.

Organizations enable Recranet Booking to support multiple properties within a single platform while keeping their data completely separate. Whether you're integrating with a single property or building a solution that spans multiple properties, all API interactions are scoped to a specific organization.

The organization defines not only ownership of data, but also the configuration that shapes how that property operates: default language, currency, timezone, branding, and feature settings.

Multi-Tenancy

Recranet Booking is built around strict multi-tenancy. This means:

Data Isolation: Data belonging to one organization is never visible to another. API requests are always scoped to a specific organization, and the system enforces this boundary at every level.

Configuration Independence: Each organization operates with its own settings. One property might use euros and Dutch as the default language, while another uses British pounds and English. These configurations don't affect each other.

User Access: Users can belong to multiple organizations, but their access to each is independent. A user might be an administrator in one organization and have read-only access in another.

API Scoping: When interacting with the API, you're always operating within the context of an organization. Most endpoints require an organization parameter or derive it from the authenticated user's context. This ensures that queries only return data the caller is authorized to access.

Organization settings

Organizations have extensive configuration options that control how the property operates.

Localization: Default language, timezone, date format, and currency. These settings affect how information is displayed to guests and staff.

Branding: Logo, colors, and styling used in guest-facing communications and documents.

Reservation rules: Minimum and maximum stay lengths, advance reservation windows, check-in/check-out times, and cancellation policies.

Communication: Email templates, automated message triggers, and notification preferences.

Payment: Connected payment providers, deposit requirements, and payment timing rules.

Integrations: Enabled third-party connections and their configuration, including channel managers, access control systems, and external services.

Organizations are the entry point for every integration with Recranet Booking. Understanding the organization model helps you:

• Scope your requests correctly – Every API call operates within an organization context
• Respect data boundaries – Never mix data between organizations
• Configure appropriately – Understand which settings affect your integration
• Handle multi-organization scenarios – Build solutions that work across multiple organizations when needed

When building an integration, you'll typically start by identifying which organization(s) you're working with. From there, all other entities (accommodations, reservations, guests) are accessed within that organizational context.