REST API
The etg24 developer platform provides two primary integration protocols: REST for deterministic system-to-system integrations and MCP for autonomous AI agents. Both interfaces operate against the same unified property management domain, enforce identical capability scopes, and produce verifiable audit logs.
Property Management API
The Property Management API provides programmatic access to tenant portfolios, units, contacts, documents, and workflows. It is maintained across two API versions:
| Version | Base URL | Lifecycle Status |
|---|---|---|
| v2 | https://api.etg24.de/propertymanagement/v2 | Active production API |
| v1 | https://api.etg24.de/propertymanagement/v1 | Deprecated (sunset on January 1, 2027) |
Every endpoint follows our strict CQRS pattern — segregated into read-only Queries and state-changing Commands. New to the platform? Start with our Getting Started guide and review the CQRS architecture.
→ Interactive v2 OpenAPI reference · Legacy v1 OpenAPI reference
The interactive reference documentation is generated directly from live backend OpenAPI specifications. Consult V1 deprecation & sunset and Rate limits for operational lifecycle details.
Model Context Protocol (MCP)
Our MCP servers expose property management capabilities directly to AI agents with dynamic tool discovery, runtime schema validation, and knowledge base grounding.
→ Explore the MCP server · Endpoint selection guide
Architectural foundations
- Rate limits — Concurrency policies, quota handling, and scale recommendations
- V1 deprecation & sunset — Migration timelines for legacy integrations
- Audit trail & change attribution — Discrete per-agent attribution across all requests