Version: 1.0.1

• OpenAPI Spec

Bairav Ingest API

The Ingest API accepts telemetry from software you run. It uses long-lived machine tokens, not user sessions.

Token	Prefix	Header	Used for
Sensor enrolment token	bst_	X-Sensor-Token	Sensor events and the governance channel
Ingest token	obt_	X-Ingest-Token (or Authorization: Bearer)	Security events, OpenTelemetry traces, SBOMs

Tokens are shown once when you create them and stored only as an Argon2id hash. Revoke a token to stop it working.

Common behaviour

• Every request is checked in this order: declared size, token, body size, schema, rate limit, then storage.
• Ingest is idempotent: re-sending an event ID you already sent reports it as a duplicate and changes nothing.
• Validation problems reject the single event, not the whole batch. The response lists each rejected event with a reason.
• Rate limits fail closed: if the limiter is unavailable you get 503 with Retry-After, never unlimited traffic.
• Prompts, responses and tool arguments are masked at ingest.

Authentication

API Key: SensorToken

A sensor enrolment token, bst_<8 hex>.<secret>. Create one in Settings, Sensor deployment.

Security Scheme Type:	apiKey
Header parameter name:	X-Sensor-Token

API Key: IngestToken

An ingest token, obt_<8 hex>.<secret>. Create one in Settings, Security data and telemetry.

Security Scheme Type:	apiKey
Header parameter name:	X-Ingest-Token

HTTP: Bearer Auth

The same ingest token, sent as Authorization: Bearer obt_....

Security Scheme Type:	http
HTTP Authorization Scheme:	bearer

Contact

Bairav developer support: BTG.Support@prokraya.com