kumod HTTP API

HTTP service is configured via kumo.start_http_listener.

Access Control

All HTTP endpoints are managed by KumoMTA's internal Access Control system.

Endpoints

The following endpoints are available:

• DELETE /api/admin/bounce/v1
• GET /api/admin/bounce/v1
• POST /api/admin/bounce/v1
• POST /api/admin/bump-config-epoch
• GET /api/admin/inspect-message/v1
• GET /api/admin/inspect-sched-q/v1
• GET /api/admin/memory/stats
• GET /api/admin/ready-q-states/v1
• POST /api/admin/rebind/v1
• POST /api/admin/set_diagnostic_log_filter/v1
• DELETE /api/admin/suspend-ready-q/v1
• GET /api/admin/suspend-ready-q/v1
• POST /api/admin/suspend-ready-q/v1
• DELETE /api/admin/suspend/v1
• GET /api/admin/suspend/v1
• POST /api/admin/suspend/v1
• GET /api/admin/task-dump
• GET /api/admin/trace-smtp-client/v1
• GET /api/admin/trace-smtp-server/v1
• POST /api/admin/xfer/cancel/v1
• POST /api/admin/xfer/v1
• GET /api/check-liveness/v1
• POST /api/inject/v1
• GET /api/machine-info
• POST /api/xfer/inject/v1
• GET /metrics.json
• GET /metrics
• schemas