August 15, 2026

​

Week in review

​

Updates

• Lead and deal pipeline stages — Leads and deals now follow formal pipeline stages that you can track from the broker module. Leads progress through new, contacted, viewing, qualified, and closed (won or lost). Deals move through inquiry, viewing scheduled, offer made, negotiating, under contract, and closed. This gives brokers and admins a consistent view of where every prospect sits. Learn more
• API rate limits by role — API requests are now rate-limited based on your role. Tenant endpoints allow 30 requests per minute, broker endpoints 60, and admin endpoints 120. AI endpoints are limited to 10 requests per minute per user (100 per org on PRO, 500 on BUSINESS). Rate-limited responses include Retry-After and X-RateLimit-* headers so your integrations can back off gracefully. Learn more
• Stricter lease field validation — Lease fields now enforce explicit ranges: monthly rent and security deposit accept values up to 1,000,000, late fees up to 10,000, grace days 0–30, and notes up to 10,000 characters. Rent due day is limited to 1–28. These constraints are enforced server-side to prevent invalid data from entering the system. Learn more
• Notification field deprecation — The entity_type and entity_id fields on notifications are now deprecated. Use resource_type and resource_id instead. The deprecated fields are still returned in API responses for backward compatibility but will be removed in a future release. Learn more

​

Bug fixes

• Fixed inconsistent maintenance priority labels in the API. Priority values are now strictly enforced as emergency, high, medium, or low across all endpoints.
• Fixed a case where the land property type could still be submitted when creating or filtering properties. It is now rejected on create and filter, though existing properties with this type remain visible in unfiltered results.