Every feature in QuickCasa is backed by an API. Leads, inventory, AI, websites, forms, media, analytics, cadences, integrations - if it exists in the platform, you can build on it. RESTful endpoints, API key authenticated, and designed for the property management industry.
Grab a key from the client portal, send it in the x-api-key
header, and read any resource. Same request shape in every language.
# fetch a single property curl https://api.quickcasa.ai/v1/properties/prop_8Kd2 \ -H "x-api-key: sk_live_your_key"
// fetch a single property const res = await fetch("https://api.quickcasa.ai/v1/properties/prop_8Kd2", { headers: { "x-api-key": "sk_live_your_key" }, }); const { data } = await res.json();
# fetch a single property import requests r = requests.get( "https://api.quickcasa.ai/v1/properties/prop_8Kd2", headers={"x-api-key": "sk_live_your_key"}, ) data = r.json()["data"]
One base URL, one auth header, one response envelope. Learn it once and every endpoint behaves the same way.
https://api.quickcasa.ai
/v1. Breaking changes ship under a new version, never in place.
x-api-key header. Keys are scoped to a single company and rotate from the portal.
{ success: true, data }; failure returns { success: false, error }.
Every response carries a standard status code, and the body always tells you what happened. No HTML error pages.
The API covers every domain of the platform. These are not thin wrappers - each domain has full CRUD operations, specialised queries, and business logic endpoints. The same APIs that power the client portal are the ones you build on.
Full lead lifecycle - creation, qualification, follow-ups, cadences, escalation, archival. Every CRM interaction is an API call.
The complete property hierarchy. Communities, buildings, unit types, individual units, floor plans, amenities, features, and policies at every level.
The intelligence layer. Entity configuration, AI persona management, intent detection, qualification rules, dynamic knowledge, and the full cognition pipeline.
Create and manage websites, pages, code files, components, themes, and publishing. The MCP server alone exposes 38 specialised tools.
Single-page forms and multi-step flow forms with branching logic, LLM nodes, and custom scripts. Plus custom attributes and client datastores.
Seven intake channels - voice, SMS, email, web widget, Facebook, Instagram, WhatsApp - all routing through a unified switchboard.
Upload, transform, and deliver images, videos, and documents. CDN-backed with authentication support and permanent URLs.
Dashboards, custom reports, NPS campaigns, web visitor tracking, and page visit analytics. Data in, insights out.
Follow-up cadences with external triggers (webhook, email, SMS), automated sequences, notifications, nudges, and scheduled jobs.
Inbound and outbound. Twilio, SendGrid, Meta, BuildingStack, Yardi, and custom webhook integrations. Data sync in both directions.
Employee management, role-based permissions, invitations, and company settings. Full access control for multi-tenant operations.
Linktree-style micro-sites, the translation plugin for multilingual support, experiments, and regional content restrictions.
The API works in both directions. Beyond reading and writing data, you can fire QuickCasa automations from your own systems.
POST a contact to a cadence's webhook token and the follow-up sequence starts on the spot - the same engine that runs in-app cadences, reachable from any external tool, form, or backend job.
curl -X POST \ https://api.quickcasa.ai/v1/cadence-webhooks/TOKEN \ -H "Content-Type: application/json" \ -d '{ "email": "lead@example.com" }'
Keys are issued from the QuickCasa client portal under company settings. Each key is scoped to one company and can be rotated or revoked at any time.
Yes. A dedicated sandbox surface lets you exercise endpoints against test data before you point a key at production.
The default is 100 requests per minute per key. If you need more headroom for a bulk sync or migration, get in touch.
Always as JSON with success: false and an error field, alongside the matching HTTP status code. Never an HTML error page.
Every route lives under /v1. When a breaking change is necessary it ships under a new version prefix, so your existing integration keeps working.
Both. Full CRUD across leads, inventory, media, forms, and more - the same endpoints the client portal itself calls.
The QuickCasa API is not a bolted-on afterthought - it is the platform. Every feature in the client portal, every AI conversation, every form submission, and every website publish is an API call under the hood. The same endpoints that power the product are the ones third-party developers, integration partners, and internal tools build on.
The API is organised around the domains of property management: leads and CRM, inventory and properties, AI and cognition, websites and pages, forms and data capture, communication channels, media, analytics, automation, and integrations. Each domain is a self-contained module with its own routes, types, and business logic.
Authentication uses API keys scoped to individual companies. Keys are issued through the client portal and can be rotated at any time. Rate limiting is built in, and all requests are logged for audit and debugging. Every endpoint returns consistent JSON responses with standard HTTP status codes.
The API is designed for the property management industry. That means the data models, the business logic, and the automation workflows are purpose-built for leasing teams, property managers, and real estate developers. You are not bending a generic API to fit your use case - the use case is baked in.
Every feature is API-first. If you can click it, you can call it.