HTTPHTTP Connectors for Generated Clients and Servers
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
namestringConnector name used in the designer and generated symbols.
RequiredtypeDataConnectorTypeExternal system kind. It is locked after endpoints are created.
RequiredAllowed:HTTP, gRPC, Kafka, Custom, Cron, TemporalgoImplementationimplementationRuntime adapter selected for this target language.
RequiredAllowed:net/httpcppUserverImplementationimplementationRuntime adapter selected for this target language.
RequiredAllowed:userver/httpcppCoroImplementationimplementationRuntime adapter selected for this target language.
RequiredAllowed:boost/beast-httppythonImplementationimplementationRuntime adapter selected for this target language.
RequiredAllowed:aiohttprustImplementationimplementationRuntime adapter selected for this target language.
RequiredAllowed:rust/axumtypeScriptImplementationimplementationRuntime adapter selected for this target language.
RequiredAllowed:node/httpmoduleModuleRegistered Module owning the generated public HTTP/OpenAPI contract. Required for a used HTTP connector, even with the shared service listener.
RequiredHTTP properties
HTTP-specific connection settings
useDedicatedListenerbooleanStarts a connector-owned listener instead of sharing the service HTTP server.
Default:falsehoststringListener host. Visible for a dedicated listener.
Default:0.0.0.0useDedicatedListener = trueport80..65535Listener port. Visible for a dedicated listener.
Default:8080useDedicatedListener = trueConfiguration example
type: HTTP
module: orders_api
useDedicatedListener: false