http://localhost:8082.
POST /kafka/messages/send
Publish a single message to a Kafka topic. Devset routes the message through the named connector and returns once the broker acknowledges the write.The name of the Kafka connector to use. Must match a connector saved via the Connectors API.
The Kafka topic to publish the message to.
The message key used for partition assignment. Omit to let Kafka assign a partition automatically.
The message value as a string. For JSON payloads, serialize your object to a JSON string before sending.
Optional key-value pairs to attach as Kafka message headers.
GET /kafka/topics
List all topics available on a Kafka connection. Query parametersThe name of the Kafka connector to query.
GET /kafka/messages
Fetch a page of messages from a Kafka topic, ordered newest-first. Results are cursor-paginated usingbeforeTimestamp. The maximum page size is 500 messages per request.
Query parameters
The name of the Kafka connector to read from.
The topic to read messages from.
Maximum number of messages to return. Defaults to
50. Hard limit is 500.An ISO 8601 timestamp (e.g.
2024-01-15T10:30:00Z). When provided, only messages produced before this instant are returned. Use the timestamp of the oldest message in the current page to fetch the next page.The Kafka partition this message was stored in.
The message offset within its partition.
ISO 8601 timestamp when the message was produced.
The message key, or
null if the producer did not set one.The raw message value as a string.
String key-value pairs attached as Kafka headers.
WS /ws/kafka/topic-stream
Open a WebSocket connection to stream live messages from a Kafka topic as they arrive. Devset forwards each incoming record to the client as a JSON text frame. The connection stays open until you close it. Connection URLThe name of the Kafka connector to subscribe on.
The topic to stream.
Controls where consumption starts. Use
latest to receive only new messages produced after the connection opens, or earliest to replay the topic from the beginning. Defaults to latest.GET /kafka/messages:
WebSocket connections are not authenticated. Keep the Devset engine accessible only on localhost or within a trusted network.
POST /rabbit/message/send
Publish a message to a RabbitMQ broker. You can target either a queue directly or an exchange with a routing key. Devset routes the message through the named producer connector.The name of the RabbitMQ connector to use. Must match a connector saved via the Connectors API.
The RabbitMQ queue to publish to directly. Provide either
queueName or exchange, not both.The RabbitMQ exchange to publish to.
The routing key used to route the message to bound queues. Used with
exchange.The message payload as a string. For JSON payloads, serialize your object to a JSON string before sending.
GET /rabbit/broker-resources
List the queues and exchanges available on a RabbitMQ connection. This endpoint requires the RabbitMQ Management Plugin to be enabled on your broker. If the plugin is not available, the response returns"available": false instead of raising an error.
Query parameters
The name of the RabbitMQ connector to query.
true if the RabbitMQ Management Plugin is reachable; false otherwise.Names of all queues declared on the broker. Empty when
available is false.Names of all exchanges declared on the broker. Empty when
available is false.POST /single-step/execute
Execute a single ad-hoc message production immediately, without creating or referencing a saved workflow. This is useful for quick one-off tests or exploratory development. Returns a run identifier you can use to look up events via the Engine API.The name of the connector to use for this execution.
The broker type:
kafka or rabbit.The payload content type. Defaults to
json.The Kafka topic to publish to. Required when
messageType is kafka.The RabbitMQ exchange to publish to. Used when
messageType is rabbit.The RabbitMQ routing key. Used when
messageType is rabbit.A name label for this pipeline stage.
A name label for the event being produced.
The payload fields to set. Supports Devset DSL functions such as
{ "$fn": "uuid()" } for dynamic values.Key-value pairs to attach as message headers.
Number of times to execute. Defaults to
1.Initial state map available to
$ref and $path expressions in set.Identifier of the persisted history entry for this execution.
The underlying engine run ID. Use it with
GET /engine/runs/{runId}/events to retrieve the produced events.Initial run status. Typically
PENDING immediately after submission.Number of executions that were requested.
The workflow identifier associated with this execution.
GET /single-step/history
Retrieve the history of all single-step executions performed in the current session. Results are ordered most-recent-first. Response — 200 OKUnique identifier of this history entry.
Creation timestamp in Unix epoch milliseconds.
The engine run ID associated with this execution.
The workflow identifier used for this execution.
The broker type used:
kafka or rabbit.The connector used for the execution.
The Kafka topic that was targeted, or
null for RabbitMQ executions.The RabbitMQ exchange that was targeted, or
null for Kafka executions.The RabbitMQ routing key used, or
null for Kafka executions.The stage name label used for this execution.
The event name label used for this execution.
The number of executions that were requested.
The payload definition that was used, including any DSL expressions.
The message headers that were applied.