Anthropod Documentation

curl -X POST https://anthropod.in/api/v2/chat_analytics/batch/ \
     -H "Authorization: Bearer <accountApiKey>" \
     -H "Content-Type: application/json" \
     -d '{
  "service_id": "CHAT SALES",
  "data": [
    {
      "id": "chat_demo_001",
      "customer_id": "customer_demo_001",
      "employee_id": "agent_demo_001",
      "conversation_time": 1788220800,
      "message_content": [
        {
          "actor_id": "customer_demo_001",
          "actor_type": "user",
          "message_type": "normal",
          "timestamp": 1788220800000,
          "content": {
            "text": {
              "content": "Please arrange a callback."
            }
          },
          "message_id": "message_demo_001"
        }
      ],
      "reopened": 0,
      "lead_source": "Website",
      "lead_sub_source": "Contact form",
      "crm_lead_stage": "Follow-up",
      "crm_lead_sub_stage": "Callback requested",
      "crm_location": "Delhi",
      "customer_phone_number": "+919876543210",
      "campaign_id": "campaign_123",
      "campaign_batch_id": "batch_123",
      "tag": "Sales",
      "tag2": "New lead",
      "tag3": "Priority",
      "crm_followup_time": 1788307200,
      "crm_lead_created_at": 1788134400,
      "reprocess": 0
    }
  ]
}'

Submit chat conversations for asynchronous analysis. HTTP 200 with a nonempty processing_id acknowledges receipt; not completed analysis. conversation_time uses epoch seconds; each message timestamp uses epoch milliseconds. Receive results through your dashboard-configured callback. Chat Analytics guide. Each record supports optional lead source, CRM stage/substage, follow-up and lead creation times, location, customer phone, campaign identifiers, and tags. The full input schema below defines these fields; reprocess defaults to 0. A null processing_id means initiation was not confirmed, even with HTTP 200. Contact support before resubmitting.

Submit chat conversations for asynchronous analysis. HTTP 200 with a nonempty processing_id acknowledges receipt; not completed analysis. conversation_time uses epoch seconds; each message timestamp uses epoch milliseconds. Receive results through your dashboard-configured callback. [Chat Analytics guide](/chat-analytics). Each record supports optional lead source, CRM stage/substage, follow-up and lead creation times, location, customer phone, campaign identifiers, and tags. The full input schema below defines these fields; reprocess defaults to 0. A null processing_id means initiation was not confirmed, even with HTTP 200. Contact support before resubmitting.

Authentication

AuthorizationBearer

Existing private account API key from Developer Hub. Keep it on your backend.

Request

This endpoint expects an object.

service_idstringRequired

Authorized project/service name from Developer Hub.

datalist of objectsRequired

Between 1 and 50 records per batch. Per-record CRM, campaign, tag fields are described below.

Response

Batch initiation result. Acceptance requires a nonempty processing_id; a null value does not confirm acceptance.

processing_idstring or null

Batch identifier for tracking processing results. Acceptance requires a nonempty identifier. The existing endpoint can return HTTP 200 with null when initiation fails; contact support before resubmitting.

timestamplong

Request receipt time in Unix epoch seconds.

Errors

400

Bad Request Error

401

Unauthorized Error

403

Forbidden Error

500

Internal Server Error