Knowledge BaseKnowledge Base

Setting Up the Paraspot Connector

Connect ParaSpot into Wazzi via API key — kick off pre- and post-stay inspection scans, pull damage and cleanliness reports, and manage the unit / property / tenancy roster straight from your AI assistant.

August 12, 2026
6 min read

Path: Connectors → ParaSpot → Configuration

What this connector does

ParaSpot is an AI-driven property-inspection platform — it scans a unit before and after every stay, flags damage and cleanliness issues, and generates comparison reports so owners and managers can settle disputes with photographic evidence. The ParaSpot connector exposes that surface to Wazzi as MCP tools so your team's AI assistants can pull inspection reports, kick off new scans, and manage the unit / property / tenancy roster without leaving the chat.

Wazzi authenticates with a Bearer API key. You provide your ParaSpot API key and (optionally) a custom base URL; Wazzi sends Authorization: Bearer <key> on every outbound request. No OAuth flow, no token rotation cycle — one key, valid until you revoke it.

The Wazzi connector exposes 17 tools grouped by domain:

  • Units (4 tools) — list, create, update, remove units.
  • Properties (3 tools) — create, update, remove properties (the parent of units).
  • Scans & reports (5 tools) — generate a scan link, get the inspection link for a unit, poll scan status, list a unit's reports, fetch a specific report, list past scans.
  • Tenancies & inspection config (4 tools) — create/update tenancies, update the inspection type on a unit, update resident data.
  • Universal escape hatch — for endpoints not yet covered by a typed tool.

Before you start — getting your API key

You'll need:

  • A ParaSpot account with API access enabled on your organization.
  • Admin permission on that account so you can generate and manage API keys.
  1. Sign in to app.paraspot.com with your ParaSpot account.
  2. Open your account settings and navigate to API Access (menu wording varies by tenant — look for API / Integrations).
  3. Generate a new API key. Treat the key like a password — it grants full access to every unit and report in your ParaSpot org.
  4. Copy the API base URL from the same page — most tenants use the shared cloud endpoint, but enterprise deployments have their own base URL.

What this connector unlocks for your team

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

  • "Kick off a pre-check-in inspection scan for unit 1042 and give me the scan link."
  • "Pull the latest inspection report for the guest who checked out yesterday at 245 Oak St."
  • "List every scan that flagged damage in the last 30 days across our Phoenix portfolio."
  • "What's the status of scan <id> — is it done processing?"
  • "Create a new tenancy record for guest X starting Friday at unit 1042."
  • "Change the inspection type on unit 1042 to full-house from routine."

The exact set of available actions depends on (a) the tier your ParaSpot subscription is on and (b) which MCP toggles are flipped on for the user's group in Wazzi — see Managing Permissions.

Steps — configuring ParaSpot in Wazzi

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

You'll land on ParaSpot's Configuration tab:

ParaSpot connector Configuration tab

2. Fill in the two fields.

  • API URL — the base URL for your ParaSpot instance (from ParaSpot's API Access page). Most orgs can use ParaSpot's default cloud endpoint.
  • API Key — the key you copied from ParaSpot's API Access page. Stored encrypted at rest in Wazzi.

3. Click Test Connection.

Wazzi hits a lightweight ParaSpot endpoint on your behalf to verify the base URL + key. On success the health check reports "Connected". If the key is invalid or the URL is wrong, you'll see a specific failure reason — most commonly a 401 (bad key) or a network error (wrong URL).

4. Click Save Configuration.

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

Troubleshooting

  • "401 Unauthorized" on Test Connection. The API key is wrong or has been revoked. Most common cause: trailing whitespace when pasting. Re-copy from ParaSpot's API Access page and try again. If still failing, regenerate the key.
  • Network / DNS error on Test Connection. The API URL is wrong. Copy the exact value from ParaSpot's API Access page (including https://) — don't strip or add a trailing slash.
  • "404 Not Found" on a specific tool. The unit / property / scan id belongs to a different ParaSpot org, or was deleted. Run list_units first to discover valid ids.
  • Empty arrays on list_unit_reports. The unit hasn't been scanned in the requested window, or the report hasn't finished processing. Give a fresh scan 5–10 minutes to complete before querying.
  • generate_scan_link returns a link that expires immediately. ParaSpot scan links are short-lived by design. Generate a fresh link right before you hand it to the person doing the walkthrough.

Best practices

  • Use a dedicated user for the integration if possible. Create a service email like wazzi-api@yourdomain.com in ParaSpot and generate the key under that account — easier to audit, revoke, and rotate than reusing a personal account.
  • Rotate the API key periodically. Regenerate in ParaSpot's API Access tab every quarter and update Wazzi. Old keys remain valid until you explicitly revoke them.
  • Restrict who can invoke destructive tools. remove_unit, remove_property, and the tenancy writes are permanent changes to your ParaSpot data. Only grant those permissions to groups that need them — see Managing Permissions.
  • Use list_units before drilling into reports. ParaSpot ids are opaque — the fastest way to find the unit id you need is a filtered list call.

Frequently asked questions

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

Can I connect multiple ParaSpot accounts?
ParaSpot is a single-instance connector today. If you need to expose more than one ParaSpot account from the same Wazzi org, file a feature request for multi-instance support (similar to the High Level connector).

What happens if I revoke the API key in ParaSpot?
Wazzi's next outbound call will fail with a 401 and the connector's health check will flip to unhealthy. Generate a fresh key, paste it into the connector configuration, and click Test Connection — the connector recovers immediately.

Is the scan link secure enough to send to a resident?
Yes. ParaSpot scan links are single-purpose, short-lived URLs that authenticate the guest walkthrough session. They don't grant access to any other unit or report.

What's next

Was this article helpful?