Sedata.AI Docs

interface AuthConfig {
  type: 'bearer' | 'apiKey' | 'basic'
  token?: string
  apiKey?: string
  username?: string
  password?: string
}

The exporterAuth field on TelemetryConfig takes an AuthConfig. The same credential is forwarded to the safety-check API as x-api-key.

Fields

'bearer' | 'apiKey' | 'basic'

required

Which authentication scheme to use.

string

Required when type: 'bearer'. Sent as Authorization: Bearer <token>.

string

Required when type: 'apiKey'. Sent as x-api-key: <apiKey>.

string

Required when type: 'basic'. Currently a no-op in the exporter (the Authorization: Basic ... header is commented out — track upstream).

string

Required when type: 'basic'. Same caveat as username.

ConfigValidator enforces:

Missing fields throw at instrumentServer time.

exporterAuth: {
  type: 'bearer',
  token: process.env.SEDATA_TOKEN!,
}
// → Authorization: Bearer <SEDATA_TOKEN>

exporterAuth: {
  type: 'apiKey',
  apiKey: process.env.OTEL_API_KEY!,
}
// → x-api-key: <OTEL_API_KEY>

exporterAuth: {
  type: 'basic',
  username: 'collector',
  password: 'secret',
}

See Authentication for the full guide.