Endpoints

The CloudEvents connector exposes its full surface on the shared HTTP server (default port 9090) and is enabled by default. This page is the authoritative reference for every endpoint: the send and queue operations (POST), the SSE subscriptions (GET), their request bodies, success status codes, and query parameters. To disable the connector, set CONNECTORSCE_ENABLE=false — see Configuration.

Base URL

All endpoints are served from the shared HTTP server:

http://localhost:9090

The port is inherited from the REST transport (default 9090). See the shared HTTP server page for the middleware chain, body limits, and SSE handling that apply to every route below.

Endpoint table

The connector groups its 12 endpoints into three families — send (synchronous operations across the five messaging patterns), queue (durable-queue control), and subscribe (long-lived SSE streams).

Send endpoints

All five send endpoints accept a CloudEvent in either content mode — structured (application/cloudevents+json body) or binary (ce-* headers + raw data body). See Content modes for the wire format, and Channel resolution for how the destination channel is derived from subject or ?channel=.

The /ce/send/response endpoint is the only send endpoint with a required query parameter:

# Send a fire-and-forget event (structured mode)
curl -X POST http://localhost:9090/ce/send/event \
  -H "Content-Type: application/cloudevents+json" \
  -d '{
    "specversion": "1.0",
    "type": "com.example.order.created",
    "source": "order-service",
    "subject": "notifications",
    "data": {"order_id": "12345", "amount": 99.99}
  }'

Queue endpoints

The queue family adds durable, at-least-once delivery. send carries a CloudEvent body; receive and ack_all are control operations — the request body is ignored and all inputs come from query parameters.

POST /ce/queue/send

Send a CloudEvent to a queue channel. Returns 202 Accepted with the send result in data.

POST /ce/queue/receive

Receive (or peek at) messages from a queue. Returns 200 OK with the received messages; each message carrying ce_* tags is reconstructed as a CloudEvent, others are returned in native KubeMQ form.

POST /ce/queue/ack_all

Acknowledge (drain) all pending messages in a queue. Returns 200 OK with the ack result in data.

# Receive up to 10 messages, waiting up to 10 seconds
curl -X POST "http://localhost:9090/ce/queue/receive?channel=work-queue&client_id=worker-1&max_messages=10&wait_timeout=10"

See Queues for the full send/receive walkthrough.

Subscribe endpoints (SSE)

All four subscription endpoints are long-lived GET requests that respond with Content-Type: text/event-stream and HTTP 200. They have no request body — the subscription is configured entirely through query parameters. See SSE behavior for the frame format, keepalive, idle timeout, and reconnection semantics.

Common SSE query parameters

All four endpoints share these base parameters:

Events-store replay parameters

/ce/subscribe/events-store accepts two additional parameters that select the replay start position:

SSE connection limits

# Subscribe to events
curl -N "http://localhost:9090/ce/subscribe/events?client_id=my-client&channel=notifications"

# Subscribe to events-store, replaying from the first stored message
curl -N "http://localhost:9090/ce/subscribe/events-store?client_id=my-client&channel=audit-log&events_store_type=2"

# Reconnect to events-store, resuming after sequence 42
curl -N -H "Last-Event-ID: 42" \
  "http://localhost:9090/ce/subscribe/events-store?client_id=my-client&channel=audit-log"

Response envelope

Every endpoint returns the same response envelope. Successful responses carry the operation result in data; errors set is_error to true with a descriptive message:

{
  "is_error": false,
  "message": "OK",
  "data": { }
}

Status codes

The full error message catalog lives in CE ↔ KubeMQ mapping.

Related