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.

Can I limit what my agent is allowed to do with the Beds24 API?

Yes. Because you self-host Jentic One, your own rules decide which Beds24 operations and credentials the agent may use, so you can grant read-only calls such as GET /bookings or GET /inventory/rooms/availability while withholding everything else. Beds24 carries its targets in the request body rather than the URL path, so you scope by operation rather than by resource path, and write operations like POST /bookings or POST /inventory/rooms/calendar are excluded unless you add them. Your long-life or refresh token is held by your Jentic One instance and injected only for the operations you have allowed.