A catalogue for your property portal
Build the public website against the documented property and location endpoints. Access is configured for the agency and the API key’s scopes. Keep private credentials on your server; do not expose them in browser code.
Send enquiries to the agency
POST /v1/leads/inquiries accepts supported enquiry data. The documented success response includes status and lead_id. Configure your form against the OpenAPI contract instead of assuming that every internal CRM field is public.
The public API uses its documented status, data and count envelope where applicable. Consult the reference for required fields, pagination and errors.
Keep website and automation responsibilities clear
The API connects the catalogue and enquiries. An incoming website request is not proof that a WhatsApp conversation is open. Messaging rules, enabled capabilities and the client’s contact path remain part of the implementation.
External API access is included in Profesional and Agencia and available through the applicable add-on in Esencial. Bespoke website work is quoted separately.