Anthropod Documentation

List and retrieve APIs return the native analysis payloads already used by Anthropod webhooks. Lists return these records in data[] with pagination; retrieval returns one record in data.

Inputs

Input	Contract
`service_id`	Required for conversation and customer analytics. Use a service belonging to your account.
`time_field`	Conversation lists: `conversation_time`. Customer lists: `last_interaction_at`. Defaults to that resource’s field.
`start_time`, `end_time`	Required for lists. Integer Unix epoch seconds; start inclusive, end exclusive; maximum 31 days.
`filter`	Optional dashboard filter object, URL-encoded as JSON. Use `and` conditions containing `field`, `operator`, and `value`; optionally `module` for configured analytics parameters. Maximum 50 conditions and 16 KB.
`limit`, `sort_order`, `cursor`	List-only: limit 1–50 (default 20); asc/desc (default desc); use the returned next cursor with unchanged filters.
Record identifier	Retrieve one conversation or customer by ID. No dates or include selector are needed.

Use channel=call or channel=chat to narrow conversation lists. Customer conversation history is filtered by the explicit customer relationship within the service.

Outputs

Field	Format
`conversation_analytics`	Native conversation modules. Each module retains its existing `version` and `analytics` when stored. Customer analytics and timeline are excluded from conversation records.
`customer_analytics`	Native accumulated customer results. Returned by customer endpoints.
`meta_analytics`	Stored metadata: call duration, talk time, languages, CRM fields, or chat response times and message counts, depending on source data.
`audio_to_text.transcript`	Complete call transcription text.
`chat_transcription.transcript`	Complete chat transcription text.
`request_data`	Original integration input as exposed by the analytics webhook.
`timeline`	Customer timeline object keyed by its stored entry IDs. Returned by customer endpoints.

Available modules, fields and null values depend on configuration and processing state. The API preserves their stored keys and types. Customer profiles represent the current accumulated state; date filters do not recreate historical snapshots.

Parameters and subparameters

Results remain keyed by their configured parameter names. ans retains its actual type: string, number, boolean, object, array, or null. Explanations and source references are returned when stored. subparameters remains a keyed object, with the same result structure recursively.

{
  "business_insights": {
    "version": 3,
    "analytics": {
      "callback_priority": {
        "ans": "High",
        "explanation": "The customer requested a callback tomorrow.",
        "explanation_with_source": [
          {
            "text": "Please call me tomorrow.",
            "sources": [
              {
                "segment_id": "S1",
                "start_timestamp": "00:00:02.000",
                "end_timestamp": "00:00:04.500"
              }
            ]
          }
        ],
        "subparameters": {
          "callback_requested": {
            "ans": true,
            "explanation": "Customer requested a callback."
          }
        }
      },
      "interested_locations": {
        "ans": [
          "Delhi",
          "Mumbai"
        ],
        "explanation_with_source": []
      }
    }
  }
}

Agent Feedback retains analytics.parameters and analytics.overall. Summaries, concerns, dispositions, templates and other modules retain their existing module-specific outputs. The API reference describes these fields and shows complete call, chat, and customer responses.

Larger downloads

Use Create export for larger datasets. Exports use the existing dashboard CSV layout and return a CSV download link. Each job supports up to 31 days, 100,000 records and 200 MiB (209,715,200 bytes). Split longer periods into adjacent windows.