Written by Ryo — August 12

The three event types available today — recommendations.updated, reservations.ingested, and flags.detected — can support a range of workflows. Here are a few starting points.

Listen for flags.detected and send a Slack message or an owner email as soon as a listing trips a flag, instead of waiting for a scheduled check.

Listen for recommendations.updated and push the new price straight into your own app, dashboard, etc as soon as it changes, instead of polling on a schedule.

Listen for reservations.ingested and stream new reservations into your BI tool or data warehouse as they land, instead of running a nightly export job.

Listen for flags.detected, then pull the listing's full KPI history and use it to auto-create a ticket or task for your revenue management team — with the relevant context already attached.

Note: Pairing this with the Scoreboards endpoint lets you show where the flagged listing ranks against the rest of your portfolio on the metric that matters, not just that it was flagged.

Route any of the three event types into a bot that posts to a channel your team already uses, so pricing changes and new flags show up where people are working instead of in a report someone has to go check.