API & Automation
Use AirROI's price-recommendation API to calculate a base price and daily rates for a property. Your application owns stored settings, availability, review, and any separate publishing integration.
The two-call workflow
Keep the read-only recommendation steps separate from decisions and channel writes.
- 01 · Calculate
Send property inputs, base price, settings, and current calendar. Read prices, explanations, and warnings.
- 02 · Review
Check business limits, skipped rules, changed availability, and which dates are approved.
- 03 · Publish separately
Send only approved updates through your channel integration. Reconcile per-date acknowledgments.
| Step | Endpoint | What to use next |
|---|---|---|
| Estimate a property reference rate | POST /price-recommendation/base-price | recommended_base_price and the response currency |
| Calculate nightly rates | POST /price-recommendation/calendar-prices | recommendations, explanations, and warnings |
You can skip the first call if you already have a base price in the correct currency. Both calls are stateless: they do not create a managed listing or publish rates.
Start here
Follow the quickstart for a complete server-side example. Add current calendar evidence before enabling occupancy, gap, or adjacent-day rules. Then define which warnings should pause publishing.
- Price Recommendation API Quickstart
Run a complete Python example that gets a base price, requests calendar prices, and inspects explanations and warnings.
- Calendar Data Guide for Price Recommendations
Map available, reserved, and blocked nights correctly, supply rule evidence, and avoid confusing input dates with the response horizon.
- Price Recommendation API Errors and Warnings
Distinguish failed requests from successful recommendations with missing evidence, and choose a deliberate recovery policy.
- Build a Safe Automated Pricing Workflow
Separate calculation from publishing, persist rule settings, manage retries, and protect channel rates with reviewable safeguards.
Guides versus the API reference
These guides explain implementation decisions and examples. The API reference specifies required fields, validation ranges, supported currencies, and response schemas. Use both: the guide for the workflow, the reference for the contract.
Need the pricing concepts first? Read Fundamentals and Pricing Rules.
Pricing through an AI client
Both recommendation endpoints are also available through the existing
AirROI MCP server. Use airroi_recommend_base_price, then pass its
returned price and currency to airroi_recommend_calendar_prices. The tools use
the same API key and paid credits, return explanations and warnings, and do not
save property settings or publish rates. Calendar results include the complete response inline,
with nightly recommendations, explanations, stay restrictions, coverage, and warnings.
Omitted or null start_date and end_date return the full one- to two-year calendar
from today in the property's timezone; either inclusive boundary narrows the
output to a window. See the MCP pricing workflow.
