Kiko C. Still no luck unfortunately.
Pretty sure I've tried every which way, here's an example of what I'm testing in postman:
curl --location 'https://app.phoenix.arize.com/v1/span_annotations' \
--header 'accept: application/json' \
--header 'Content-Type: application/json' \
--header 'OTEL_EXPORTER_OTLP_HEADERS: api_key=redacted' \
--header 'PHOENIX_CLIENT_HEADERS: api_key=redacted' \
--header 'PHOENIX_COLLECTOR_ENDPOINT: https://app.phoenix.arize.com' \
--header 'Authorization: Bearer redacted' \
--header 'api_key: redacted' \
--data '{
"data": [
{
"span_id": "a2f0cd65be677102",
"name": "string",
"annotator_kind": "HUMAN",
"result": {
"label": "test",
"score": 0,
"explanation": "test"
},
"metadata": {}
}
]
}'
For context, initial spans are being traced from my DSPy-instrumented backend (this is working), I then pass the span ID to a nextjs app frontend where the user gives feedback. The annotation is submitted from there, and this is where I'm running into the error.
This was all working a few weeks ago, so I wonder if some of the recent auth changes on the phoenix end have killed my API key or something? Is there a way I can generate a fresh one?
