GET
/
v0
/
traces
curl --request GET \
  --url https://api.avidoai.com/v0/traces \
  --header 'x-api-key: <api-key>' \
  --header 'x-application-id: <api-key>'
[]

Authorizations

​
x-api-key
string
header
required

Your unique Avido API key

​
x-application-id
string
header
required

Your unique application ID. Get this from the Connections page in Avido.

Query Parameters

​
skip
integer
default:0

Number of items to skip (for pagination)

Required range: x >= 0
Example:

0

​
limit
integer
default:25

Number of items per page

Required range: 1 <= x <= 100
Example:

25

​
startDate
string

Start date (ISO8601) for filtering traces.

Example:

"2025-01-09T14:47:56Z"

​
endDate
string

End date (ISO8601) for filtering traces.

Example:

"2025-01-09T14:47:56Z"

Response

200
application/json
Successfully retrieved traces with steps
​
id
string
required

Unique Trace ID (UUID).

Example:

"123e4567-e89b-12d3-a456-426614174000"

​
timestamp
string
required

ISO-8601 datetime when the trace was created.

Example:

"2025-01-05T12:34:56.789Z"

​
referenceId
string

An optional reference ID to link the trace to an existing conversation or interaction in your own database.

Example:

"123e4567-e89b-12d3-a456-426614174000"

​
metadata
object | null

Arbitrary metadata (e.g., userId, source). String inputs are parsed as JSON or wrapped in { raw: val }.

Example:
{ "userId": "123", "source": "chatbot" }
​
testId
string | null

The associated Test if this was triggered by an Avido eval

​
steps
object[] | null

The steps associated with the trace.

Schema for LLM trace events.

Get a single application by IDGet a single trace by ID