Skip to main content
The admin endpoints give you operational control over a running InferenceWall instance: hot-reload configuration without downtime, view request statistics, and inspect the active runtime settings.
All admin endpoints require the admin API key (iwk_admin_ prefix). Requests made with a scan key return 401 Unauthorized.

POST /v1/admin/reload

Hot-reload signatures and policies from disk without restarting the server. Use this after adding custom signatures or changing your policy file — changes take effect immediately.

Example

After calling /v1/admin/reload, confirm the changes by calling GET /v1/signatures to verify your new signatures appear, or GET /v1/policies to verify threshold changes.

GET /v1/admin/stats

Retrieve system statistics for the running instance, including request counts, decision distribution, and block rates.

Example

Response fields

number
Total number of scan requests processed since the server started.
object
Breakdown of decisions by verdict.
number
Fraction of all requests that resulted in a block decision (0.0–1.0).
number
Server uptime in seconds since the last start.

GET /v1/config

Read the active runtime configuration, including environment variable values and resolved settings.

Example

Response fields

string
The host address InferenceWall is bound to (IW_HOST).
number
The port InferenceWall is listening on (IW_PORT).
string
The active deployment profile: lite, standard, or full (IW_PROFILE).
string
The active log level (IW_LOG_LEVEL).
string
TLS mode: auto, off, or a path to a certificate (IW_TLS).
string
Resolved path to the custom signatures directory (IW_SIGNATURES_DIR).
string
Resolved path to the active policy file (IW_POLICY_PATH).
string
Redis URL for distributed sessions, or null if not configured (IW_REDIS_URL).