Setting Up the Reva Connector

Path: Connectors → Reva → Configuration

What this connector does

Reva is a vacation-rental review management platform — it aggregates guest reviews from every channel you list on (Airbnb, Vrbo, Booking, Google, internal channels, etc.) into a single dashboard with sentiment, ratings, and staff-attribution analytics. The Reva connector exposes that data to Wazzi as MCP tools so your team's AI assistants can pull review metrics, look up specific reservations, list units and their ratings, and run staff performance reports without leaving the chat.

Wazzi authenticates via HTTP Basic auth. You provide your Reva account email and an API key generated in Reva; Wazzi base64-encodes them together and sends an Authorization: Basic … header on every outbound request. No OAuth flow, no token rotation cycle — one key, valid until you revoke it.

The Wazzi connector exposes 11 tools total, mirroring the official API reference:

• Companies (1 tool) — list every Reva company your user has API access to.
• Channels (1 tool) — the review channels (Airbnb, Vrbo, Booking, internal, etc.) configured per company.
• Nodes (1 tool) — the hierarchical groupings (regions, buildings, brands) you've set up to organize units.
• Units (2 tools) — list units with rich filters; fetch aggregated ratings for a single unit.
• Reviews (3 tools) — list company-wide reviews, list reviews on a specific unit, and create an internal review.
• Reservations (1 tool) — look up a single reservation by Reva ID.
• Reports (1 tool) — pull the staff performance report.
• Universal escape hatch (1 tool) — call any Reva endpoint with arbitrary method/path/query/body for things not yet wrapped by a typed tool.

Before you start — getting your API key

You'll need:

• A Reva user account with API product access on at least one company. If you're not sure whether you have API access, an admin on your company's Reva account can confirm.
• Admin or owner access on that user account (so you can generate keys under Integrations).

1. Sign in to app.joinreva.com with your Reva account.
2. Click your user dropdown in the top right of the dashboard.
3. Select Integrations.
4. Generate a new API key, or copy your existing one. Treat the key like a password — it gives full read access to every company your user is authorized for.
5. Note the email you signed in with — it's the other half of the credential pair.

Reference: Reva's official API docs live at revadocs.readme.io. Auth flow is documented under Authentication.

What this connector unlocks for your team

Once configured, members with the right MCP permissions can ask Claude / ChatGPT / Cursor things like:

• "What's the average rating across all our units in the Coachella Valley region?"
• "Show me the 10 most recent 1- and 2-star reviews from the last 30 days."
• "Pull staff performance data for our property managers for the last quarter."
• "What were the reviews on Property X from Airbnb in Q3?"
• "Look up reservation <id> — was it ever reviewed?"
• "Create an internal review for unit Y rating 5 with description '…'."

The exact set of available actions depends on (a) the companies your Reva user has API access to and (b) which MCP toggles are flipped on for the user's group in Wazzi — see Managing Permissions.

Steps — configuring Reva in Wazzi

1. From the Connectors catalog, click Configure on the Reva tile.

You'll land on Reva's Configuration tab:

2. Fill in the two fields.

• Email — the email address of the Reva user account that owns the API key. Stored encrypted at rest in Wazzi.
• API Key — the key you copied from Reva's Integrations page. Stored encrypted at rest in Wazzi.

3. Click Test Connection.

Wazzi calls GET /v1/companies on your behalf using your credentials. On success the health check reports the number of companies your token has access to — e.g. "Connected — 1 company (Acme)". If the token is valid but no companies are attached, you'll see "Connected — no companies granted to this token" — that's an account-side configuration issue rather than a code problem.

4. Click Save Configuration.

Reva moves to the Active section of the catalog and the dot turns green.

Troubleshooting

• "401 Unauthorized" on Test Connection. Either the email or the API key is wrong. Most common cause: trailing whitespace when pasting the key. Re-copy from Reva's Integrations page and try again. If still failing, regenerate the key — old keys can be silently revoked if your account permissions were changed.
• "Connected — no companies granted to this token". Your user account exists and the API key is valid, but Reva hasn't granted your user API access on any company yet. Ask a Reva admin on the target company to add API access for your account, then re-run Test Connection.
• "403 Forbidden" on a specific tool. The company_id you passed is one your user doesn't have API access to. Run list_companies first to discover which company UUIDs are in your scope, then pass only those.
• Empty arrays returned from list endpoints. The company really has zero of that resource in the requested filter window, or your filter is too restrictive. Try widening the date range or removing optional filters.
• "404 Not Found" on get_reservation. The reservation_id is wrong, or Reva hasn't received that reservation from your PMS yet. Cross-check the id by extracting it from a review record's reservation_id field — that's the canonical Reva-side reference.

Best practices

• Use a dedicated user for the integration if possible. Create a service email like wazzi-api@yourdomain.com in Reva and grant it API access on the companies that need it. Easier to audit, revoke, and rotate than reusing a personal account.
• Rotate the API key periodically. Regenerate in Reva's Integrations tab every quarter and update Wazzi. Old keys remain valid until you explicitly revoke them in Reva.
• Restrict who can invoke create_review in Wazzi. Internal reviews land in your Reva account permanently. Only grant the create-review permission to groups that legitimately need it — see Managing Permissions.
• Use list_companies first when scripting. Reva's API is multi-tenant under one user — knowing your company UUID set is the prerequisite for every other call.
• Use list_company_nodes + parent_node_ids to scope queries. If you've organized units into regional or brand-based nodes, you can scope review and report queries to those groupings instead of pulling the whole company — much faster for large portfolios.

Frequently asked questions

Does Wazzi store my credentials in plaintext?
No. Both the email and API key are encrypted at rest with per-org keys and only decrypted at the moment an outbound call is made.

Why does Reva need an email AND a key?
Reva's API uses HTTP Basic authentication, which requires both a username and password. The "password" in this case is the API key. The email identifies which Reva user the key is bound to, so your audit log on Reva's side correctly attributes API calls back to a specific account.

Can I connect multiple Reva user accounts?
Reva is a single-instance connector. If you need to connect more than one Reva user from the same Wazzi org, file a feature request for multi-instance support (similar to how the High Level connector works). For now, pick the user whose company access best matches your needs.

What if I need an endpoint that doesn't have a typed tool?
The call_reva_endpoint tool is a universal escape hatch — call any Reva REST path with GET or POST and arbitrary query / body. Useful for endpoints Reva ships before we typed-wrap them.

Are reviews I create via the API publicly visible?
No — create_review lands the review in Reva's internal channel, which is for your team's records and analytics. It doesn't push to Airbnb, Vrbo, or any external channel.

How do I tie a review to a reservation?
When calling create_review, pass the optional reservation_provider_id field with the reservation ID from your source PMS (Streamline, Track, etc.). Reva will link the review to the underlying stay.

What's next

• Restrict who in your org can invoke Reva actions: Managing Permissions.
• Wire Reva into your AI tool: Connecting Claude or Connecting ChatGPT.
• Browse other connectors: Browsing the Connectors Catalog.