Skip to content
POST/api/v1/siem/inbound/{source}

Ingest events from SIEM source

Inbound SOAR trigger: an external SIEM posts an ACTION and this endpoint executes it. `:source` must be splunk, sentinel, qradar or generic_webhook — it selects the vendor signature scheme and is recorded on the audit row. The `X-EvalGuard-Project` and `X-EvalGuard-Token-Id` headers are both required and select one `siem_inbound_tokens` row (mint and manage those at /api/v1/siem/inbound/tokens); a revoked token is rejected 401, and an action outside that token's `allowed_actions` list is rejected 403 and recorded as skipped. Actions: quarantine_key / unquarantine_key (flip api_keys.quarantined_at), force_rotate and block_user (revoke api_keys), escalate_review (open a security_incidents row), custom (audit-only, no enforcement). Every AUTHORIZED action attempt writes a `siem_inbound_actions` row (executed|failed), and an action outside the token's allow-list is recorded as skipped; auth, signature and rate-limit failures — and an idempotent replay — write no new row. Rate limited per token (default 30/min, 429). Optional `idempotency_key` replays a prior result as { status:'skipped', idempotent:true }. Authentication: the per-token shared-secret HMAC your SIEM sends (the SiemInboundSignature scheme), together with the `X-EvalGuard-Project` and `X-EvalGuard-Token-Id` headers that select the token. An `eg_` API key is not read here; the token's own `allowed_actions` list authorizes the action, so no API-key scope is published.

Authentication

SIEM shared-secret HMAC. Sign the raw body with the secret issued to this SIEM. The header depends on source: X-EvalGuard-Signature + X-EvalGuard-Timestamp (300s skew) for generic_webhook, X-Splunk-Signature for splunk, X-QRadar-Signature for qradar, Authorization: SharedKey <secret> for sentinel.

X-EvalGuard-Project and X-EvalGuard-Token-Id are also required — they select the siem_inbound_tokens row holding the secret and its allowed_actions, which authorizes the action instead of API-key scopes. An eg_ API key is not read on this path.

Parameters

source in pathrequired

Source identifier (e.g., 'splunk-prod-1')

string

Response

200 example

{
  "success": true
}

All status codes

200Ingested.
401Inbound token missing or invalid.

Code samples

cURL

# {source} is shown with an EXAMPLE value — replace it with real values.
curl -X POST \
  https://evalguard.ai/api/v1/siem/inbound/splunk-prod-1 \
  -H "Authorization: Bearer $EVALGUARD_API_KEY"

TypeScript

// The TypeScript SDK (@evalguard/sdk) exposes TYPED methods — runEval,
// getEval, runSecurityScan, checkFirewall, … — not a generic request().
// For an arbitrary endpoint, call it directly:
// {source} is shown with an EXAMPLE value — replace it with real values.

const res = await fetch("https://evalguard.ai/api/v1/siem/inbound/splunk-prod-1", {
  method: "POST",
  headers: { Authorization: `Bearer ${process.env.EVALGUARD_API_KEY}` },
});
console.log(res.status, await res.json());

Python

# The Python SDK (pip install evalguardai) exposes TYPED methods on
# EvalGuardClient — run_eval, get_eval, … — not a generic request().
# For an arbitrary endpoint, call it directly:
# {source} is shown with an EXAMPLE value — replace it with real values.

import os
import requests

headers = {"Authorization": f"Bearer {os.environ['EVALGUARD_API_KEY']}"}

response = requests.request("POST", "https://evalguard.ai/api/v1/siem/inbound/splunk-prod-1", headers=headers)
print(response.status_code, response.json())

Go

package main

import (
	"context"
	"fmt"
	"net/http"
	"os"
)

// {source} is shown with an EXAMPLE value — replace it with real values.
func main() {
	req, _ := http.NewRequestWithContext(context.Background(), "POST", "https://evalguard.ai/api/v1/siem/inbound/splunk-prod-1", nil)
	req.Header.Set("Authorization", "Bearer "+os.Getenv("EVALGUARD_API_KEY"))
	resp, err := http.DefaultClient.Do(req)
	if err != nil { panic(err) }
	defer resp.Body.Close()
	fmt.Println(resp.Status)
}

Errors

401

Other Integrations endpoints