Loading your workspace
How organization admins create API keys, authenticate requests, and publish vacant units to external apps using the public vacant-houses endpoint.
Organization API keys let approved integrations read public vacancy data without signing into the dashboard. Typical uses include website vacancy widgets, partner listing portals, and internal tools that need a machine-readable unit feed.
Keys are scoped to one organization and should be rotated when staff change or an integration is retired. Only organization admins should create and revoke credentials.
Open Organization Settings, choose API Keys, name the integration, optionally set an expiry date, and create the key. Copy the secret immediately because it is shown only once at creation.
Store keys in your integration secret manager—not in chat threads or shared documents. Revoke keys that are no longer needed instead of leaving dormant credentials active.
Authenticated integrations call GET /api/public/vacant-houses with Authorization: Bearer <organization-api-key>. The key must be active, unexpired, and include vacant_units:read in its public listings permission set.
Successful responses return up to 200 vacant units with pricing, location, property context, and image references. Rate limiting is 60 requests per minute per key or client IP; 429 responses include Retry-After.
Confirm vacancies are published for the units you expect, then test the endpoint from staging or a controlled client before pointing a public website at production.
Monitor last-used timestamps in settings to verify the integration is calling the API as expected. Pair API usage with your vacancy marketing workflow so pricing and availability stay accurate.
Organization admins create and revoke API keys from Organization Settings. Other staff roles do not manage integration credentials.
Revoked keys immediately fail authentication with 401 responses. Update the integration with a new active key before deactivating the old one to avoid downtime.
No. The public vacant-houses endpoint returns published vacancy fields only. Tenant, payment, and lease records stay inside authenticated app workflows.
Marketing
How property teams publish vacant units, help tenants discover homes by location, and handle enquiries with clearer property context.
Kenya
How Kenyan landlords, agencies, and caretakers organize tenants, leases, rent, water billing, vacancies, maintenance, and reporting in one workspace.
Billing
A practical guide to moving from spreadsheets to structured rent charges, payment records, unpaid tenant follow-up, and month-end reporting in EstateDesk.
Start with the records your team uses every day, then layer on billing, caretaker coordination, vacancies, and reporting as the portfolio grows.