Skip to main content
Most Agnost API errors return a JSON body with an error string:

Common errors

SymptomLikely causeFix
No events appearWrong org ID or endpointConfirm org ID in Settings -> Organization and use https://api.agnost.ai or https://otel.agnost.ai/v1/traces.
401/403 on dashboard APIMissing JWT/API key or wrong org scopeUse Authorization: Bearer <jwt> or x-api-key plus the right x-org-id.
400 on ingestionMissing required field or invalid UUIDValidate session_id, event_id, and user_data.user_id.
OTel traces missingHeader not attached or exporter endpoint is wrongSet OTEL_EXPORTER_OTLP_HEADERS=X-Agnost-Org-ID=<your-org-id> and use /v1/traces when the SDK expects a trace URL.
Tool inputs missingInput capture disabled or framework did not export contentCheck SDK config and framework telemetry settings.

Debugging checklist

  1. Send one test event.
  2. Open Raw logs in the Agnost dashboard.
  3. Confirm the event has the expected org ID, user ID, session/conversation ID, and agent/tool name.
  4. Check Tools or Conversations depending on the integration.
  5. If using OpenTelemetry, confirm your app can reach otel.agnost.ai.