# Errors

> Common API and ingestion errors

Most Voxmith API errors return a JSON body with an `error` string:

```json theme={null}
{
  "error": "Invalid request body"
}
```

## Common errors

| Symptom | Likely cause | Fix |
| - | - | - |
| No events appear | Wrong org ID or endpoint | Confirm org ID in Settings -> Organization and use `https://api.voxmith.com` or `https://otel.voxmith.com/v1/traces`. |
| 401/403 on dashboard API | Missing JWT/API key or wrong org scope | Use `Authorization: Bearer <jwt>` or `x-api-key` plus the right `x-org-id`. |
| 400 on ingestion | Missing required field or invalid UUID | Validate `session_id`, `event_id`, and `user_data.user_id`. |
| OTel traces missing | Header not attached or exporter endpoint is wrong | Set `OTEL_EXPORTER_OTLP_HEADERS=X-Voxmith-Org-ID=<your-org-id>` and use `/v1/traces` when the SDK expects a trace URL. |
| Tool inputs missing | Input capture disabled or framework did not export content | Check SDK config and framework telemetry settings. |

## Debugging checklist

1. Send one test event.
2. Open **Events** in the Voxmith dashboard.
3. Confirm the event has the expected org ID, user ID, session/conversation ID, and agent/tool name.
4. Check **Tool calls** or **Conversations** depending on the integration.
5. If using OpenTelemetry, confirm your app can reach `otel.voxmith.com`.

## Related pages

* [Authentication](/authentication)
* [OpenTelemetry troubleshooting](/otel#troubleshooting)

## Next steps

* [Quickstart](/quickstart): compare your setup with the recommended path.
* [Authentication](/authentication): verify headers and organization routing.
* [Events](/using-events): confirm whether telemetry reached Voxmith.