Addis AI

GET /v1/studio/analyses

List the analyses of your Studio conversations, newest first, filtered by agent, time and whether they need attention.

Lists your conversation analyses one page at a time, newest first by analysed_at. Each item has the shape of one analysis, with the labels you corrected in Studio. Conversations from the agent test panel are left out.

curl "https://api.addisassistant.com/v1/studio/analyses?needs_attention=true&limit=20" \
  -H "x-api-key: $ADDIS_API_KEY"

Query parameters

Prop

Type

Response

{
  "data": [
    {
      "conversation_id": "c1000000-0000-4000-8000-000000000010",
      "agent_id": "a1000000-0000-4000-8000-000000000010",
      "status": "completed",
      "summary": "A new customer asked about the price of the 200 watt home solar kit...",
      "priority": "normal",
      "needs_human": false,
      "analysed_at": "2026-10-25T07:10:30+00:00"
    }
  ],
  "next_cursor": "1792912230000000_c1000000-0000-4000-8000-000000000010"
}

The item above is shortened; every item has all the fields of one analysis.

Keeping a copy in sync

To keep your own copy current:

  1. Ask for since the newest analysed_at you have stored.
  2. Follow next_cursor until it is null.

since is inclusive, so the analysis made at exactly that time comes again: store analyses by conversation_id. A conversation analysed again in Studio comes back with its new analysed_at. A label you correct in Studio does not change analysed_at, so to pick up a correction, read that conversation again by ID.

Prop

Type

Errors

StatusCodeMeaning
400invalid_requestA query parameter is not valid; error.param names it.
400invalid_cursorThe cursor is not one this endpoint returned.
401unauthorized, invalid_api_keyThe x-api-key header is missing or not a valid key.
429risk_rate_limitedYour account is temporarily limited. See Rate Limits.

Errors use the error object.

Edit on GitHub

Last updated on

On this page