Retrieve a specific OpenLineage event using its unique event ID.
Returns a single stored OpenLineage event, including its event type, timestamp, producer, run and job details, processing status, and any associated assets and relationships.
GET https://[hostname]/api/v1/openlineage/events/{eventId}
Request Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| eventId | string | Yes | Unique identifier for the event |
Request Examples
Each example shows how to call this endpoint with the documented method, URL, headers, and request body format.
curl -X GET "/api/v1/openlineage/events/{eventId}" \
-H "Authorization: Bearer <JWT>"
fetch("/api/v1/openlineage/events/{eventId}", {
method: "GET",
headers: {
"Authorization": "Bearer <JWT>"
}
})
.then(res => res.json())
.then(data => console.log(data));
import json
import requests
url = "/api/v1/openlineage/events/{eventId}"
headers = {
"Authorization": "Bearer <JWT>"
}
payload = None
response = requests.get(url, headers=headers)
print(response.json())
package main
import (
"fmt"
"io"
"net/http"
)
func main() {
body := http.NoBody
req, _ := http.NewRequest("GET", "/api/v1/openlineage/events/{eventId}", body)
req.Header.Set("Authorization", "Bearer <JWT>")
client := &http.Client{}
resp, _ := client.Do(req)
defer resp.Body.Close()
body2, _ := io.ReadAll(resp.Body)
fmt.Println(string(body2))
}
Success Responses
This payload returns the stored OpenLineage event for the requested event ID, including event identity and lifecycle fields such as id, eventType, eventTime, producer and job/run references, processing status, the original event payload, created relation and asset references, and service timestamps.
For customers, this confirms the event exists and provides the full event record needed for traceability, troubleshooting, and lineage verification.
{
"id": "string",
"eventType": "string",
"eventTime": "string",
"producer": "string",
"runId": "string",
"jobNamespace": "string",
"jobName": "string",
"status": "string",
"payload": {
"eventType": "string",
"eventTime": "string",
"producer": "string",
"schemaURL": "string",
"run": {
"runId": "string",
"facets": "value"
},
"job": {
"namespace": "string",
"name": "string",
"facets": "value"
},
"inputs": [
{
"namespace": "string",
"name": "string",
"facets": "value",
"inputFacets": "value",
"outputFacets": "value"
}
],
"outputs": [
{
"namespace": "string",
"name": "string",
"facets": "value",
"inputFacets": "value",
"outputFacets": "value"
}
]
},
"assetsCreated": [
"string"
],
"relationsCreated": [
"string"
],
"createdAt": "string",
"processedAt": "string"
}Error Responses
This payload uses the standard error structure with statusCode, code, error, message, and optional validationErrors entries containing path and message.
For customers, this means the supplied eventId did not match a stored event record and the message fields provide the actionable error context.
Representative payload generated from the response schema.
{
"statusCode": 0,
"code": "string",
"error": "string",
"message": "string",
"validationErrors": [
{
"path": "string",
"message": "string"
}
]
}