How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Langfuse LegacyScoreV1 API

The LegacyScoreV1 API from Langfuse — 2 operation(s) for legacyscorev1.

Langfuse LegacyScoreV1 API is one of 28 APIs that Langfuse publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include LegacyScoreV1. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.0.1, at version 1.0.

Requests are made against the base URL https://cloud.langfuse.com/api/public.

2 operations 2 paths 5 schemas 1 DELETE1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://cloud.langfuse.com/api/public
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Langfuse LegacyScoreV1 API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (BasicAuth).

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 1 DELETE, 1 POST. Each is listed below with its method, path, parameters, and response codes.

LegacyScoreV1 2
POST
/api/public/scores
Create a score (supports both trace and session scores)
legacy_scoreV1_create body → 200400401403404405
DELETE
/api/public/scores/{scoreId}
Delete a score (supports both trace and session scores)
legacy_scoreV1_delete 1 param → 204400401403404405

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are legacyCreateScoreRequest (14 properties), legacyCreateScoreResponse (1 property). Each schema is shown below with its type and property counts.

CreateScoreValue
The value of the score. Must be passed as string for categorical and text scores, and numeric for boolean and numeric scores
legacyCreateScoreRequest
object
14 properties 2 required
legacyCreateScoreSource
string
Source values accepted when creating a score via the public REST API. EVAL is reserved for internal evaluator outputs and is intentionally not exposed here — u…
legacyCreateScoreResponse
object
1 property 1 required
ScoreDataType
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

langfuse-legacyscorev1-api-openapi.yml Raw ↑

Other APIs Langfuse publishes across the network.

Langfuse AnnotationQueues API
Langfuse BlobStorageIntegrations API
Langfuse Comments API
Langfuse DatasetItems API
Langfuse DatasetRunItems API
Langfuse Datasets API
Langfuse Health API
Langfuse Ingestion API
Langfuse LegacyMetricsV1 API
Langfuse LegacyObservationsV1 API
Langfuse LlmConnections API
Langfuse Media API
Where this information came from

This is an independent, third-party profile of Langfuse LegacyScoreV1 API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.