Custom endpoints

When a protocol isn’t built in, you can plug your own endpoint into the engine. A custom endpoint is selected from config by name and delegates to a factory you register programmatically before starting routes.

Config

output:
  custom:
    name: "my_sink"
    config: { target: "internal://thing" }

The custom endpoint works as a route input or output.

Implementing it

Implement the CustomEndpointFactory trait and register your type before starting routes. The factory receives the config JSON and builds an endpoint that speaks the engine’s MessageConsumer / MessagePublisher traits (in mq_bridge::traits), so your endpoint participates in batching, middleware, and ack/nack exactly like a built-in one.

See also

• custom (endpoint) reference — the authoritative field list.
• Learn the architecture → Extending mq-bridge — the trait and registration mechanics.
• Custom middleware — the middleware equivalent.