Beds24 API V2

Name: Beds24 API V2 API
Brand: Beds24 API V2
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceOrder ManagementapiKey38 EndpointsREST

For Agents

Manage short-term rental bookings, room inventory and availability, properties, and channel-manager sync to Airbnb and Booking.com through Beds24's 38-endpoint property management API.

Install Jentic One Beta

Connect the Beds24 API V2 to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Beds24 API V2, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Beds24 API V2 API.

Create, retrieve, modify, and cancel guest bookings across all linked channels

Update room availability, calendar overrides, and fixed prices for inventory control

Send and read in-thread booking messages between hosts and guests

GET STARTED

Start building with Beds24 API V2 API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Beds24 API V2 API for, with concrete tasks.

★ Channel-managed short-term rental operations

Hosts and property managers use Beds24 as the source of truth for inventory, then push availability and rates to Airbnb and Booking.com so the same room cannot be double-sold. The API's Channels endpoints let an integration update Airbnb listings and pull Booking.com reservations, while /inventory/rooms/calendar drives availability. Bookings created directly via POST /bookings flow back out to channels automatically.

Mark room 4421 unavailable from 2026-07-15 to 2026-07-22 via /inventory/rooms/calendar and confirm the block has propagated to the linked Airbnb listing

Guest messaging and check-in automation

Operations teams automate guest communications around the booking lifecycle using the booking-messages endpoints. /bookings/messages reads the thread for a reservation and posts new messages that appear in the host inbox and on the linked channel where supported. Combined with /bookings, an automation can send check-in instructions a day before arrival and read replies overnight.

For booking 99821 arriving tomorrow, post a check-in instructions message containing the door code and Wi-Fi password to the booking thread

Guest payments via the Stripe channel

Beds24's Stripe channel endpoints let property managers issue payment requests, capture deposits, and reconcile guest payments without leaving the PMS. The Channels - Stripe operations create a payment intent against a connected Stripe account and the booking record is updated when the guest completes payment, removing the need for a separate ledger.

Issue a 200 EUR Stripe deposit request against booking 99821 and mark the booking as paid once the guest completes the payment

AI agent integration for property managers

Property managers run AI agents through Jentic to handle routine PMS tasks: mark rooms unavailable, send check-in messages, pull arrivals reports, or push rate changes during high season. The agent searches Jentic for the operation, loads the schema, and executes with the Beds24 token held in the Jentic vault, so the long-life token never appears in agent context.

Through Jentic, find Beds24's bookings list operation and return all bookings arriving on 2026-08-01 across properties 1101 and 1102 with guest contact details

Key Endpoints

38 endpoints — jentic publishes the only available openapi specification for beds24 api v2, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/bookings

List bookings with date and property filters

POST

/bookings

Create a new booking

POST

/bookings/messages

Post a message on a booking thread

GET

/inventory/rooms/availability

Read room availability

POST

/inventory/rooms/calendar

Update the calendar for a room

POST

/inventory/fixedPrices

Set fixed nightly prices for date ranges

GET

/properties

List properties on the account

GET

/authentication/token

Issue a token using a refresh token

GET

/bookings

List bookings with date and property filters

POST

/bookings

Create a new booking

POST

/bookings/messages

Post a message on a booking thread

GET

/inventory/rooms/availability

Read room availability

POST

/inventory/rooms/calendar

Update the calendar for a room

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Beds24 long-life token (or refresh token plus organization header) is stored encrypted in the Jentic vault. Jentic injects the token and organization headers at execution time, so credentials never enter agent context.

Intent-based discovery

Agents search Jentic by intent (e.g. list arriving bookings or block a room calendar) and Jentic returns the matching Beds24 operation with its input schema, so the agent calls /bookings or /inventory/rooms/calendar without browsing the wiki.

Time to first call

Direct Beds24 integration: 2-4 days to wire token rotation, scope handling, and channel-specific edge cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Beds24 API V2 API through Jentic.

Why is there no official OpenAPI spec for Beds24 API V2?

Beds24 does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Beds24 API V2 via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Beds24 API V2 use?

Beds24 uses a token sent in the token header. You generate either a long-life token or a short-lived token via GET /authentication/token using a refresh token, with optional scopes per token. Integration partners also pass an organization header. Jentic's vault stores the long-life token or refresh token and injects the headers at execution time.

Can I sync Airbnb listings and Booking.com reservations through the Beds24 API?

Yes. The Channels - Airbnb endpoints sync listings, rates, and availability with Airbnb, and the Channels - Booking.com endpoints handle reservation pulls and channel settings. Pair these with /inventory/rooms/calendar so a single calendar update propagates to all linked channels.

How do I send a guest message on a booking through Jentic?

Search Jentic for send a message on a Beds24 booking to find POST /bookings/messages. Load the schema and execute with the bookingId and the message body. Use GET /bookings/messages to read the thread back. Where the channel supports message-pass-through (Airbnb), the message will appear in the guest's channel inbox.

Does the Beds24 API support guest payments?

Yes, via the Channels - Stripe endpoints. They create payment requests against a connected Stripe account and update the booking when the guest pays. The PMS holds the canonical paid status, so finance reconciliation does not need to query Stripe directly.

How do I refresh a Beds24 token?

Call GET /authentication/token with your refresh token to receive a new short-lived access token. Use GET /authentication/details to confirm the token's scopes and DELETE /authentication/token to revoke a token when rotating credentials.

What are the rate limits for the Beds24 API?

Beds24 enforces per-account credit limits documented at wiki.beds24.com rather than fixed requests-per-second. If you receive HTTP 429 responses or credit-exhausted errors, back off and retry, and contact Beds24 support to request additional credits for production integrations.

Beds24 API V2

Connect the Beds24 API V2 to your agent

Capabilities

Start building with Beds24 API V2 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs