Docs / API

API overview

Authenticate, send events, and attach environment and release metadata — everything you need to integrate without an SDK.

Authentication

Use a project-scoped ingest credential over HTTPS. Prefer header auth; never expose keys in public client code.

X-API-Key: tal_live_YOUR_KEY
# or
Authorization: Bearer tal_live_YOUR_KEY

Event shape

Single-event and batch ingest accept JSON bodies for exceptions and structured logs. Include a message or exception payload, plus optional tags for filtering.

{
  "message": "Payment failed",
  "level": "error",
  "environment": "production",
  "release": "1.4.2",
  "exception": {
    "type": "RuntimeException",
    "value": "Gateway timeout",
    "stacktrace": []
  },
  "tags": {
    "area": "checkout"
  }
}

Environments & releases

Set environment (for example production or staging) and optional release so the dashboard can filter issues and correlate deploys. Fingerprints are computed server-side — clients never send a fingerprint field.

Traces (advanced)

Official SDKs send traces via native span ingest. Prefer enableTracing / tracesSampleRate on the SDKs. If you already run an OpenTelemetry Collector, you can export OTLP/HTTP JSON traces to POST /otlp/v1/traces with a project API key that includes spans:write. Protobuf OTLP is not accepted. Host/k8s metrics and logs are out of scope.

exporters:
  otlphttp:
    traces_endpoint: https://api.newtalaria.com/otlp/v1/traces
    headers:
      Authorization: Bearer tal_live_YOUR_KEY
    encoding: json

service:
  pipelines:
    traces:
      receivers: [otlp]
      exporters: [otlphttp]