Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

CONNECT EAP

Core architecture principles

  • Last UpdatedAug 06, 2026
  • 1 minute read

CONNECT is designed around several fundamental architectural principles that ensure consistency, scalability, and security across all services:

Service-oriented architecture

CONNECT adopts a modular approach where functionality is distributed across specialized services, enabling independent scaling and evolution of components:

  • Each functionality area is exposed through dedicated service endpoints.

  • Consistent URL patterns following /api/account/{accountId}/{service}/{instanceId}/v1/... structure.

  • Versioned APIs (most services offer v1, with key services like Stream Management also offering v2).

Multi-tenancy

The platform is designed to securely serve multiple organizations while maintaining isolation and security boundaries:

  • Account and instance identifiers are fundamental routing parameters.

  • Services operate within account and instance security boundaries.

  • Authorization based on OAuth2 token authentication.

RESTful design

CONNECT embraces modern RESTful principles for intuitive and consistent interaction patterns:

  • Standard HTTP methods (GET, POST, PUT, DELETE) for CRUD operations.

  • Resource-oriented endpoints.

  • Problem Details pattern (RFC 7807) for error reporting.

  • Consistent status code usage across services.