Veetal

Hotel rate-shopping and destination-demand feeds delivered as a metered API: per-property accommodation rates and cross-channel rate parity (the same room compared across booking sites, board basis and cancellation policy inside one schema), availability, room types and property imagery, guest reviews, market-level occupancy and demand, inbound flight demand, and a destination events calendar. Documented endpoints include a per-property rate endpoint, a per-property parity endpoint, a dated booking-site location-search endpoint, plus separate availability and flight-demand datasets.

Open buyer room →

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks Veetal and files the sample in your catalog — private to you.

Start 7-day trialNothing is charged until the trial ends.

Coverage

Universe, instruments and categories.

Industry: HotelsFinancial Exchanges & DataApplication Software
Instruments: equities

Dataset card

Type: not stated
Format: Tabular JSON delivered over a documented REST API under a single bearer token, credit-metered, with the vendor also exposing the same data to agent tooling through a Model Context Protocol interface and prebuilt recipe prompts
Volume: Dense per property rather than broad in population: each monitored property generates a matrix of channel x board basis x cancellation policy x arrival date x poll date, so a 5,000-property portfolio polled daily yields order 10^7-10^8 observations a year. Published coverage counts are not stated on this page, so the monitored universe is the key unknown
Users: N/A for consumers — a developer-facing metered API sold to revenue agencies, operators and travel technology firms. Commercial adoption appears early-stage, evidenced by a self-serve 1,000-credit free tier with no card required rather than a published customer base
History: 1 years
Update frequency: not stated
Growth: Active and very early — the product page is being actively built out with application recipes, per-dataset landing pages, developer documentation and an agent-tooling interface added alongside the core rate and parity feeds
Launched: ~2024-2025 — the company entity registers as created around Nov-2024, and the current developer-platform packaging with credit tiers and recipes reads as a recent launch
Delivery: not stated
Entity mapping: not stated
Sample: not stated
Point-in-time: not stated
Licence: not stated

supplier index read from their site