Skip to main content

For vendors & partners

You build a product on top of etg24 — an ERP bridge, an AI assistant, a voice agent — and want your product to work against customer data through the etg24 API.

No self-registration for vendors

Vendors and product partners do not self-register. If you want an integration, you contact us directly.

The onboarding path

Integration with etg24 follows a short, structured process:

  1. Contact us — describe your product and the integration you have in mind.
  2. Conversation — we align on scope, capabilities and the right integration model together.
  3. Integration — you build against the API; we configure your integration type, capability tags and credentials.
  4. Tile in the integration list — once approved, your product appears as a tile in the etg24 integration list, so customers can discover and connect it.

Before you contact us

Prepare these five things — they let us give you a fast, concrete answer:

  • Product overview — what your product does and for whom.
  • Intended use case — which workflows your product covers on the customer side.
  • Which endpoints / events you need — check the REST API reference and the webhook events to be specific.
  • Auth model on your side — how your own product authenticates (OAuth, API keys, tokens).
  • Expected volume — how many customers, requests, and events you expect.

Integration models

There is no one-size-fits-all integration. We agree on the model that fits your product — for example whether your product connects per customer, across many customers with one credential, or as a platform-level partner. Access control is capability-based: every endpoint your integration reaches is explicitly granted. Details in Permission scopes.

After integration

Your integration is tied to a capability-gated API surface. You can find the exact reachable endpoints in the Property Management v2 reference — endpoint access is managed per integration type.