SAService ArchitectDocumentation

/

Data connectorsHTTP

Data connector HTTP

HTTP connector

HTTP server or client transport.

When to use

Configure this object once per external system or listener. Add concrete routes, methods, topics or schedules as endpoints inside it.

Behavior

Owns transport-level connection and implementation settings.
Can contain multiple endpoints.
Input and Sink streams reference endpoints, not the connector directly.

General properties

Connector identity and language-specific runtime adapters

PropertyTypeDescription

namestring

Connector name used in the designer and generated symbols.

Required

typeDataConnectorType

External system kind. It is locked after endpoints are created.

RequiredAllowed: HTTP, gRPC, Kafka, Custom, Cron, Temporal

goImplementationimplementation

Runtime adapter selected for this target language.

RequiredAllowed: net/http

cppUserverImplementationimplementation

Runtime adapter selected for this target language.

RequiredAllowed: userver/http

cppBoostImplementationimplementation

Runtime adapter selected for this target language.

RequiredAllowed: boost/beast-http

pythonImplementationimplementation

Runtime adapter selected for this target language.

RequiredAllowed: aiohttp

rustImplementationimplementation

Runtime adapter selected for this target language.

RequiredAllowed: rust/axum

typeScriptImplementationimplementation

Runtime adapter selected for this target language.

RequiredAllowed: node/http

moduleModule

Shared API type module used by generated handlers.

HTTP properties

HTTP-specific connection settings

PropertyTypeDescription

useDedicatedListenerboolean

Starts a connector-owned listener instead of sharing the service HTTP server.

Default: false

hoststring

Listener host. Visible for a dedicated listener.

Default: 0.0.0.0useDedicatedListener = true

port80..65535

Listener port. Visible for a dedicated listener.

Default: 8080useDedicatedListener = true

Configuration example

type: HTTP
useDedicatedListener: false