Vultr Message Center (1.0.0)

Accepts a delivery request. The service will persist the delivery to the database, then asynchronously call the customer's endpoint via HTTPS POST with an HMAC-SHA256 signature.

The response is 201 with no body — the delivery is queued and will be attempted asynchronously. Use the GET /v1/deliveries/{id} endpoint to check the delivery status.

Retrieve the status of a delivery by its UUID.

View the current status of the message center service.

Schedules background consumption of a RabbitMQ queue. Messages are buffered into Redis and flushed to the logs database table when the queue is deleted or an [END_OF_STREAM] sentinel message is received.

Returns 202 Accepted immediately. Actual consumption runs in a background worker process.

Opens a Server-Sent Events (SSE) stream that consumes messages directly from the specified RabbitMQ queue in real-time. Each message is delivered as an SSE message event with the message body in the data field.

The stream stays open until the client disconnects, the queue is deleted, or the idle timeout (default 300s) is reached.

Retrieves queue statistics from the RabbitMQ management API, including message counts, consumer count, and idle state.

Retrieve log entries for a given entity. The {prefix} identifies the log type (e.g. order) and {id} is the entity identifier (e.g. the order UUID).

The RabbitMQ queue name follows the convention {prefix}-{id}.

Behaviour:

• If the background consumer has already flushed the logs to the database, all entries are returned as a single JSON response (status: complete).
• If the consumer is still buffering messages in Redis, a text/event-stream (SSE) response is returned so the client can read entries in near real-time.
• If neither Redis nor the database has any data, a 404 is returned.

Serves an HTML page with an Alpine.js-based log viewer that connects to the SSE stream at /v1/log/{prefix}/{id} and displays log entries in real-time.