Creates a new score. Upserts on id for updates if score with id exists.
Creates a new span. Sunset warning: this is the deprecated Langfuse v3 ingestion API. It is shut down on November 16, 2026, except for score events: from that date it accepts only score-create events and rejects all other event types, including this one. To write scores, prefer POST /api/public/scores; see the Scores API docs. To write traces and observations, always prefer upgrading to the current Python and JS SDKs. If you use custom auto-instrumentation, send them to the OpenTelemetry endpoint (POST /api/public/otel/v1/traces), for example with curl; see the OpenTelemetry integration docs. To read data back, use the v4 read APIs; see the Observations API docs and the Metrics API docs. The only path to live data is OpenTelemetry ingestion combined with GET /api/public/v2/observations and GET /api/public/v2/metrics. All other public APIs may have data delays of several minutes.
Updates span based on id. Sunset warning: this is the deprecated Langfuse v3 ingestion API. It is shut down on November 16, 2026, except for score events: from that date it accepts only score-create events and rejects all other event types, including this one. To write scores, prefer POST /api/public/scores; see the Scores API docs. To write traces and observations, always prefer upgrading to the current Python and JS SDKs. If you use custom auto-instrumentation, send them to the OpenTelemetry endpoint (POST /api/public/otel/v1/traces), for example with curl; see the OpenTelemetry integration docs. To read data back, use the v4 read APIs; see the Observations API docs and the Metrics API docs. The only path to live data is OpenTelemetry ingestion combined with GET /api/public/v2/observations and GET /api/public/v2/metrics. All other public APIs may have data delays of several minutes.
Creates a new generation. Sunset warning: this is the deprecated Langfuse v3 ingestion API. It is shut down on November 16, 2026, except for score events: from that date it accepts only score-create events and rejects all other event types, including this one. To write scores, prefer POST /api/public/scores; see the Scores API docs. To write traces and observations, always prefer upgrading to the current Python and JS SDKs. If you use custom auto-instrumentation, send them to the OpenTelemetry endpoint (POST /api/public/otel/v1/traces), for example with curl; see the OpenTelemetry integration docs. To read data back, use the v4 read APIs; see the Observations API docs and the Metrics API docs. The only path to live data is OpenTelemetry ingestion combined with GET /api/public/v2/observations and GET /api/public/v2/metrics. All other public APIs may have data delays of several minutes.
Updates a generation based on id. Sunset warning: this is the deprecated Langfuse v3 ingestion API. It is shut down on November 16, 2026, except for score events: from that date it accepts only score-create events and rejects all other event types, including this one. To write scores, prefer POST /api/public/scores; see the Scores API docs. To write traces and observations, always prefer upgrading to the current Python and JS SDKs. If you use custom auto-instrumentation, send them to the OpenTelemetry endpoint (POST /api/public/otel/v1/traces), for example with curl; see the OpenTelemetry integration docs. To read data back, use the v4 read APIs; see the Observations API docs and the Metrics API docs. The only path to live data is OpenTelemetry ingestion combined with GET /api/public/v2/observations and GET /api/public/v2/metrics. All other public APIs may have data delays of several minutes.
Creates an event. Sunset warning: this is the deprecated Langfuse v3 ingestion API. It is shut down on November 16, 2026, except for score events: from that date it accepts only score-create events and rejects all other event types, including this one. To write scores, prefer POST /api/public/scores; see the Scores API docs. To write traces and observations, always prefer upgrading to the current Python and JS SDKs. If you use custom auto-instrumentation, send them to the OpenTelemetry endpoint (POST /api/public/otel/v1/traces), for example with curl; see the OpenTelemetry integration docs. To read data back, use the v4 read APIs; see the Observations API docs and the Metrics API docs. The only path to live data is OpenTelemetry ingestion combined with GET /api/public/v2/observations and GET /api/public/v2/metrics. All other public APIs may have data delays of several minutes.
Deprecated event type. Sunset warning: this is the deprecated Langfuse v3 ingestion API. It is shut down on November 16, 2026, except for score events: from that date it accepts only score-create events and rejects all other event types, including this one. To write scores, prefer POST /api/public/scores; see the Scores API docs. To write traces and observations, always prefer upgrading to the current Python and JS SDKs. If you use custom auto-instrumentation, send them to the OpenTelemetry endpoint (POST /api/public/otel/v1/traces), for example with curl; see the OpenTelemetry integration docs. To read data back, use the v4 read APIs; see the Observations API docs and the Metrics API docs. The only path to live data is OpenTelemetry ingestion combined with GET /api/public/v2/observations and GET /api/public/v2/metrics. All other public APIs may have data delays of several minutes.
Deprecated event type. Sunset warning: this is the deprecated Langfuse v3 ingestion API. It is shut down on November 16, 2026, except for score events: from that date it accepts only score-create events and rejects all other event types, including this one. To write scores, prefer POST /api/public/scores; see the Scores API docs. To write traces and observations, always prefer upgrading to the current Python and JS SDKs. If you use custom auto-instrumentation, send them to the OpenTelemetry endpoint (POST /api/public/otel/v1/traces), for example with curl; see the OpenTelemetry integration docs. To read data back, use the v4 read APIs; see the Observations API docs and the Metrics API docs. The only path to live data is OpenTelemetry ingestion combined with GET /api/public/v2/observations and GET /api/public/v2/metrics. All other public APIs may have data delays of several minutes.
Creates a new trace. Upserts on id for updates if trace with id exists. Sunset warning: this is the deprecated Langfuse v3 ingestion API. It is shut down on November 16, 2026, except for score events: from that date it accepts only
score-createevents and rejects all other event types, including this one. To write scores, preferPOST /api/public/scores; see the Scores API docs. To write traces and observations, always prefer upgrading to the current Python and JS SDKs. If you use custom auto-instrumentation, send them to the OpenTelemetry endpoint (POST /api/public/otel/v1/traces), for example with curl; see the OpenTelemetry integration docs. To read data back, use the v4 read APIs; see the Observations API docs and the Metrics API docs. The only path to live data is OpenTelemetry ingestion combined withGET /api/public/v2/observationsandGET /api/public/v2/metrics. All other public APIs may have data delays of several minutes.