Skip to main content
On this page

Full API coverage

etg24 is API-first. There is no “internal feature set” that outpaces the API surface.

What “full coverage” means

  • Full functional coverage — everything the application can do is available through the API. Every endpoint in the app is derived from the same definitions that power the REST reference and the MCP tool reference.
  • Full data coverage — everything the application stores is reachable. There is no class of data that lives only in the UI.

One surface, two protocols

The REST API and the MCP server are two views of the same surface. A capability that exists in the app exists as a REST endpoint, and is exposed to AI agents as an MCP tool — unless it is deliberately excluded.

This is why you can rely on the platform for complete automations: whatever your team can do by hand, an integration can do programmatically.

What this unlocks

  • Migrations — onboard an entire company: import every object, unit, contact, and document through the API.
  • Two-way syncs — keep an external system in step with etg24 data, field by field.
  • Agents that act — AI agents get the same complete toolbox as humans, with the guardrails from Authentication & security.