From key to hotels importing data — in minutes
No onboarding call and no configuration days. The whole setup is three calls — or the same three things clicked in the dashboard.
Get your API key
Sign up and copy it from the dashboard. One header, no OAuth, nothing to refresh — and 1,000 free credits to spend.
Create the hotel yourself
No provisioning ticket and no setup weeks: every entity on your account is yours to create, by UI or by API.
Schedule your imports
First run by hand, with its credit estimate before you press. Then a frequency, and the Feed stays fresh on its own.
# 01 — does my key work? curl "https://api.veetal.app/v2/account/customer-info" \ -H "veetal-api-key: $KEY" # 02 — put my hotel on the account curl -X POST "https://api.veetal.app/v2/account/accommodation" \ -H "veetal-api-key: $KEY" \ -d '{ ... }' # 03 — is the import done? curl "https://api.veetal.app/v2/account/imports" \ -H "veetal-api-key: $KEY"
Base URL https://api.veetal.app · request body in the account reference
Applications already built on it
Every one runs on the key you just created — asked for inside your assistant over MCP, or cloned and run in your own stack.
Event Demand Radar
Every event that will move hotel demand in a city, with roomnights, pressure and booking window.
Competitor Rate Grid
The classic rate-shopping grid: your hotel against its comp set, live from Booking.com.
Import a hotel's reputation from Booking
Take any hotel from Booking, add it to Veetal and pull its multi-OTA reputation — score, review count and category breakdown from Booking.com, Tripadvisor and Google — ready to read over the API.
Put a reputation panel on your own website
One score built from every OTA your hotel is listed on, the sentiment split behind it, and which categories are actually moving — rendered on your own site, behind a proxy that keeps your API key private.
Start guide
Create the account, copy the key, make the first call. Three steps, nothing to install.
Open →Recipes
Builds that run on live data — an MCP prompt to ask for, or code to clone, with the endpoints they use.
Browse →MCP setup
Connect Claude, Cursor or ChatGPT to your account in one paste — the server URL and your key, nothing else.
Connect →API documentation
Account, Feed and Real Time: every endpoint, every parameter and what each response carries.
Read →Blog
How the datasets behave in the wild: rates, reputation, events and what the numbers actually mean.
Read →What do you want to build?
Say it in one line and we hand you back the prompt for our MCP, the recipe that already builds it, and the APIs it runs on.
