Skip to content
yaReserva

Search the site

Go to

Searches the 78 features, the 36 guides, the documentation and the frequently asked questions.

Book
The yaReserva ecosystem

Your own booking engine over the API

When your site already has its own engine and you don’t want the widget: the API that sells against your inventory, with payment always in your account.

Reading time
3 min read
Steps
7
In the panel
yaReserva ecosystem → Your own booking engine
Published

Before you start

  • Someone who maintains your hotel’s website: this one is done with a developer beside you.
  • Your payout account ready, or no booking can be charged.

When it helps and when it doesn’t

Your hotel runs on yaReserva — your inventory, prices and policies live here — but your site’s booking screen is yours. This API lets you sell against that inventory without using our widget.

Credentials

  1. Step 1: Create the connection

    In “Your own booking engine” you create the key and the secret, and optionally the authorised domains and a per-booking cap.

  2. Step 2: Store the secret straight away

    It’s shown once, when created and when rotated. If it’s lost, you rotate it and change it on your server: there is no way to see it again.

  3. Step 3: Decide whether it’s a server or browser key

    With no authorised domains the key is a server key: a request arriving from a browser is rejected even if the signature is correct. If your engine runs in the browser, declare its domains.

The flow, in four steps

  1. Step 1: Availability

    The guest searches for dates and gets rooms and rates back. Nothing available is not an error: it answers correctly with an empty list.

  2. Step 2: Quote

    They pick one and it is quoted with taxes and policy. The cancellation tiers travel one by one, not as a canned sentence, so your screen can render them in its own language and format.

  3. Step 3: Book

    With the guest’s details and one idempotency key per attempt. The same key always returns the same booking, so two simultaneous requests don’t create two bookings.

  4. Step 4: Charge

    You request the payment intent and finish the payment on your screen. With no amount, the outstanding balance is charged in full.

Who collects and what you pay

  • The charge is created in your direct-sales account. Your engine never calls the gateway to create the payment intent: our backend creates it and your screen finishes it. Creating it on your side would put the amount and currency in the client’s hands and break reconciliation with the folio.
  • Cancelling doesn’t refund the money. The charge was created in your account, so you issue the refund from your panel. The response says so, so your screen doesn’t promise the guest a refund nobody has sent.
  • Your own engine is contracted as a separate subscription. It’s billed as a full month, without proration, at that month’s current price, and it comes with its own stamping folios. Commissions don’t credit against it: “if you sell, you don’t pay” applies to the fee, and this is a different product.

Ready to try it at your hotel?

Signing up is free, and you can try the panel first in the demos.