Skip to main content

Documentation Index

Fetch the complete documentation index at: https://sedataai.mintlify.app/llms.txt

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

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

​
type
'bearer' | 'apiKey' | 'basic'
required
Which authentication scheme to use.
​
token
string
Required when type: 'bearer'. Sent as Authorization: Bearer <token>.
​
apiKey
string
Required when type: 'apiKey'. Sent as x-api-key: <apiKey>.
​
username
string
Required when type: 'basic'. Currently a no-op in the exporter (the Authorization: Basic ... header is commented out — track upstream).
​
password
string
Required when type: 'basic'. Same caveat as username.

​
Per-type validation

ConfigValidator enforces:
  • bearer requires token.
  • apiKey requires apiKey.
  • basic requires both username and password.
Missing fields throw at instrumentServer time.

​
Examples

​
Bearer

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

​
API key

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

​
Basic (validated, header not yet emitted)

exporterAuth: {
  type: 'basic',
  username: 'collector',
  password: 'secret',
}
See Authentication for the full guide.