Search reviews
Searches individual guest reviews for the credential’s scope, ordered by review date (newest first). Requires scope read:reviews.
Authorizations
Authorization: Bearer <token>. Token types resolve to the same scoped credential: a user-generated API key (casa_…, from Account settings — recommended for first-party machines and MCP clients), a partner credential access token (third-party agents; REST-only), a session JWT (the web app; org and role come from verified token claims), or a static token. API keys are group-scoped, optionally pinned to one property at creation. Personal API keys and partner credentials accept X-Property-Id to drill down to one property in the group. A property-pinned API key ignores that header. MCP OAuth connector tokens authenticate the MCP server only and are rejected on these REST routes.
Headers
Optional single-property drill-down. Narrows this request to one property in the caller's group. A property outside the group returns 403. Personal API keys and partner credentials accept this header. A property-pinned API key ignores it. Casa Layer sign-in tokens reject it.
Query Parameters
Free-text match on title, body, or guest name.
Channel name (e.g. Booking.com).
Include reviews dated on/after this ISO date.
Include reviews dated on/before this ISO date.
Only reviews with (true) / without (false) a host response.
Repeat for each profile member. A review matches when its guest id is one of these, or its stay source id is one of reservation_source_id, or it is a Reva review whose guest name overlaps reva_guest_name.
Repeat for each stay source id on the profile.
Profile display name. Matches guest_name on Reva reviews only.
Page size — rows returned per call (1–500). This is NOT a cap on the total dataset: follow next_cursor to retrieve every matching row.
1 <= x <= 500Opaque pagination token from a previous response's next_cursor. Omit for the first page. A malformed token returns 400 invalid_cursor.
Response
Matching reviews.
Keyset-pagination fields present on every list/search response. When has_more is true, re-request with cursor set to next_cursor; repeat until next_cursor is null to retrieve the full result set.