Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.secapi.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Event export

Operators need a support-friendly way to inspect request, webhook, and stream event history outside the live API response path. Omni Datastream supports filtered event listing and JSON or NDJSON exports.

​
Endpoints

  • GET /v1/events
  • GET /v1/events/export

​
Filtered event inspection

curl "$OMNI_DATASTREAM_URL/v1/events?kind=event&type=artifact.created&requestId=req_123&limit=20" \
  -H "Authorization: Bearer $OMNI_DATASTREAM_API_KEY"
Useful filters:
  • kind
  • type
  • requestId
  • since
  • limit

​
Export JSON

curl "$OMNI_DATASTREAM_URL/v1/events/export?kind=event&limit=100&format=json" \
  -H "Authorization: Bearer $OMNI_DATASTREAM_API_KEY"

​
Export NDJSON

curl "$OMNI_DATASTREAM_URL/v1/events/export?kind=webhook_delivery&since=2026-03-14T00:00:00Z&format=ndjson" \
  -H "Authorization: Bearer $OMNI_DATASTREAM_API_KEY"
Use NDJSON when downstream tooling wants line-oriented ingestion into log processors or ad hoc support scripts.

​
CLI

omni-sec events list --kind event --request-id req_123 --limit 20
omni-sec events export --kind webhook_delivery --since 2026-03-14T00:00:00Z --format ndjson

​
Operational notes

  • exports are tenant-scoped
  • request correlation is driven by Request-Id
  • support should prefer exports over direct database access for routine inspections