Training / Resort Pro plan / Lesson 11 of 12
Connecting other software: API and webhooks
You will not use these yourself, but technical buyers ask about them. This lesson gives you enough to answer confidently and to know when to bring in a developer.
- Modules
- M53 Open API · M62 Webhooks, sandbox and developer page
- Who uses it
- The customer's developers or software vendors
- Plan
- Resort Pro plan
- Where
- Settings › API Keys, Settings › Webhooks, and /api/docs
What it is for
A larger resort already has other software: an accounting package, a door-lock system, a marketing tool, perhaps its own website built by an agency. They will ask, "Can Resortiqo talk to it?" The honest answer is: yes, if their developer builds the connection, and we give them everything needed to do so.
The API, in plain words
An API is a set of doors through which another program can read or change information in Resortiqo, without a person clicking screens. Through it a program can, for example, list today's arrivals, make a booking, record a payment or mark a room clean.
Three facts worth knowing:
- It covers almost everything. Every feature in these lessons has API doors, by design. Our own staff app uses only the API, so we know it works.
- It is documented. A developer guide and a full reference are at
/api/docson the resort's address. - It respects permissions. A program can only do what its key allows.
API keys

An API key is a long secret password for a program. The Owner creates one in Settings › API Keys, gives it a name such as "Accounting sync", and ticks its scopes: the specific things it may do, such as read bookings or write payments.
Give each program its own key with the fewest scopes it needs, and revoke a key the moment it is no longer used. A key shown once at creation cannot be seen again; if it is lost, make a new one.
Webhooks
A webhook works the other way round. The customer gives Resortiqo an internet address, and Resortiqo calls that address the moment something happens: a booking made, a guest checked in, a payment received, a room cleaned. The other system can then react at once, without asking again and again.

Each call is signed with a secret, so the receiver can be sure it really came from this resort. Failed calls are retried, and a delivery log shows what was sent with a Send again button.
The sandbox
A sandbox is a pretend resort full of made-up data where a developer can try the API safely with free keys. It emails nobody. We create it once from the console.
What it connects to
We do not build the customer's connection for them as part of the plan. Their developer does, or it is separate paid Advertiqo work.
The API has no plan switch today. Although it is listed under Resort Pro, a Stay or Resort customer can also create API keys. Either a switch will be added or the API will be offered on every plan. Do not promise it as exclusive to Resort Pro.
The sandbox cannot be created yet on the live system. It counts as a second resort, and a second resort needs the hosting company's own backups to be recorded first.
Webhook retries need the server's scheduled job.
The channel manager screen (Settings › Channel manager) is in "sandbox mode": it can be set up and tried, but sends nothing to any booking site.