Live

Integrations & API

You know whether all data has arrived. For every hotel.

Manage data sources for each hotel with traffic-light status.

Get access

How it works

  1. 01

    You connect your systems by API, file or email inbox.

  2. 02

    RD030 checks for each hotel whether every delivery arrives on time.

  3. 03

    If something is missing, the traffic light shows it and names the owner.

Features

  • Traffic light per source

    You see straight away which connection runs and which does not.

  • Missing deliveries

    Missing reports and imports stand out before figures go wrong.

  • Overview per hotel

    All data sources of your hotel or hotels on one page.

  • Ownership

    Each connection documents who looks after it.

  • API, file or email inbox

    Each system is connected the way it can deliver data.

  • Health Check by email

    One email summarises whether every source has delivered.

Data sources and connection

Connection by API, file or email inbox, depending on your PMS.

We are building a connection assistant for OPERA Cloud (OHIP), Mews and Apaleo. We will announce availability once it is live.

Other PMS such as SIHOT are connected by file or email inbox.

Price

49 € / hotel / month, net

Prices net plus statutory VAT.

Get access

Goes well with

The problem today

A missing delivery often becomes apparent only in a report. Teams have to locate each source’s state and responsibility separately.

What the module does

The Integrations & API module shows every data source for each hotel with a traffic-light status. Missing or disrupted deliveries become visible. Responsibilities for each integration are documented.

  • See connection status for each source and hotel.
  • Review adapters in the shared registry.
  • Run approved requests through official APIs.
  • Use API documentation for integration.
  • Receive events through approved webhooks.
  • Identify and investigate missing deliveries.

What it looks like

Connection statesSample Hotel Berlin · BSP · 151 rooms
SourceLast deliveryStatus
PMS14:37Connected
RMS14:32Connected
Reports08:11Review
Connection states · Illustrative view with fictional data
API and webhook: illustrative schemaSample Hotel Berlin · BSP · 151 rooms

Illustrative schema, not a contractual API endpoint. Credentials and identifiers are placeholders.

GET /api/example/hotels/{hotel_id}/pickup
Authorization: Bearer {access_token}

{ "hotel_code": "BSP", "rooms": 151 }

Webhook
{ "event": "delivery.received",
  "hotel_code": "BSP", "source": "PMS" }
API and webhook: illustrative schema · Illustrative view with fictional data

Example from operations

Illustrative view with fictional data · Sample Hotel Berlin · BSP · 151 rooms

  1. Trigger

    The expected delivery for BSP is missing.

  2. Message

    The connection state flags the source for review.

  3. Response

    The responsible role checks the approved adapter and delivery.

  4. Result

    The snapshot can be put in context before the next analysis.

What it replaces

Manually checking whether reports and imports have arrived.

Roles and permissions

Visibility follows approved hotels, hotel groups and platform-core roles. Administration manages assignments; commercial works within its approved hotel context.

Frequently asked questions

Is the module available now?

Live. Access and approved integrations are agreed per hotel. Extensions are only described as live once availability is confirmed.

Does the module replace our PMS or RMS?

No. RD030 is the shared work and control layer above them. Decisions and changes take place in the systems approved for them.

Which data may be connected?

Only official APIs, approved data access, report and file imports, and exports you provide.

Status and outlook

Live

Live. Access and approved integrations are agreed per hotel. Extensions are only described as live once availability is confirmed.

Related modules