List extracted data-collection values across voice and text

{
  "data": {
    "windowDays": 30,
    "agentId": null,
    "fields": [
      {
        "id": "demo_agendada",
        "top": [
          {
            "value": false,
            "count": 88,
            "voice": 30,
            "text": 58
          },
          {
            "value": true,
            "count": 19,
            "voice": 11,
            "text": 8
          }
        ]
      },
      {
        "id": "pais",
        "top": [
          {
            "value": "Colombia",
            "count": 57,
            "voice": 21,
            "text": 36
          },
          {
            "value": "México",
            "count": 24,
            "voice": 9,
            "text": 15
          },
          {
            "value": null,
            "count": 4,
            "voice": 1,
            "text": 3
          }
        ]
      }
    ]
  }
}

For each data-collection field the agents extract, the 10 most frequent values over calls and text conversations created in the window, with per-source counts. Fields are sorted by id; values within a field by count descending. Only records that carry extracted data count, and deleted calls are excluded. For up to 50 values of one field over text only, use GET /api/analytics/conversations/field/{field}.

Unlike the text-only endpoint, values keep the JSON type the analysis stored: 5 (number) and "5" (string) are different entries, and true is a boolean.

No data. fields is an empty array when nothing in range was extracted. A record where the field exists without a value appears as value: null.

Idempotency. Read-only; safe to retry.

Access

Required scope: read. Signed-in users need the owner, admin, member or viewer role.
Rate limit: Analytics — 30 requests/min per workspace, shared with the rest of /api/analytics/*, in addition to the general API budget of your plan. See Rate limits.
Plan: Available on every plan. Requires an active subscription (active, trialing or past_due); without one the request is refused with 403 BILLING_ERROR (metadata.kind: subscription_required).

Authentication

AuthorizationBearer

Workspace API key: jl_ followed by 64 lowercase hex characters, created by the workspace owner in the dashboard (Settings → API Keys) and sent as Authorization: Bearer jl_.... The plaintext is shown once, at creation; Jelliu stores only a SHA-256 hash. A workspace can hold up to 25 active keys.

Scope	GET / HEAD	POST / PUT / PATCH / DELETE	Admin-only routes
`read`	Yes	No	No
`write`	Yes	Yes	No
`full`	Yes	Yes	Yes

Operations restricted to admins or owners reject keys without the full scope with 403, and say so in their description. No key, whatever its scope, can mint or revoke API keys or rotate a webhook secret — that requires a signed-in owner session. A revoked key stops authenticating within about 10 seconds. See Authentication.

Query parameters

daysintegerOptional1-365Defaults to 30

Window in days ending now. Never rejected: a value outside 1-365, 0 or a non-numeric value falls back to 30, and decimals are floored.

agentIdstringOptionalformat: "uuid"

Restrict to one agent. A malformed id is a 400 (never silently ignored). An empty value means no filter.

Response

Data-collection roll-up.

dataobjectOptional

Errors

400

Bad Request Error

401

Unauthorized Error

403

Forbidden Error

429

Too Many Requests Error