Full API coverage

etg24 is engineered API-first. Our web and mobile applications consume the exact same backend endpoints available to your integrations. There is no private, unexposed feature set that can only be reached through the graphical interface.

What complete coverage means in practice

• Full functional parity: Every business operation feasible in the web app — creating units, adjusting tenancy contracts, scheduling owner meetings, uploading and classifying documents — exists as an API endpoint.
• Full data accessibility: Every entity attribute stored in the platform is exposed. You will never encounter “UI-only” fields that cannot be queried or updated programmatically.

One backend architecture, two integration protocols

REST and MCP are two interfaces into the same underlying domain model:

1. REST API: Designed for deterministic system-to-system integrations, scheduled ETL jobs, and web applications.
2. Model Context Protocol (MCP): Designed for AI agents that require dynamic tool discovery and execution.

Any capability available via REST can be exposed to AI agents as an MCP tool with consistent validation rules, permissions, and audit logging.

Core integration scenarios

• Full portfolio migrations: Onboard a new management mandate by bulk-importing properties, units, tenant contacts, and historical documents entirely via API.
• Bi-directional CRM & ERP synchronizations: Keep local accounting systems (e.g. Domus, Wodis, RealEstate ERPs) synchronized in real time with etg24.
• Autonomous agent workflows: Grant AI assistants the exact tools required to process service tickets and draft communications, bounded by robust Identity & delegation guardrails.