Activity Log

Your own system, such as a dialer or a CRM, can write activity entries onto a conversation’s Teambox timeline. Log a call, a WhatsApp call, a meeting, an email, an SMS or a note, and your team sees it in the chat next to the messages. These three endpoints add, list and delete those entries.

Where it shows

• In the Teambox web chat window, between the messages. Each entry is placed by its occurredAt time.
• In the Assign tab history in the right panel.
• In the assignment-history popover.
• Live in any chat that is open when you add or delete an entry.

Entries are not shown in these places:

• The Teambox mobile app (not yet).
• The dashboard Leads page.
• GET /v2.0/conversations/assignment-history. Read them with GET /v2.0/conversations/activity instead.

How an entry looks

• type sets the icon.
• title is the bold line.
• note is the second line.
• by shows as “by Rahul Sharma via API”. Without it, the entry shows “via API”.
• linkUrl adds a link. It uses linkLabel as its text, or “Open link” when you leave the label out.

Finding the conversation

Adding and listing entries both need to know which chat. Pass one of these:

• conversationId: the id returned by GET /v2.0/chats/conversations.
• contactId, with optional channel and businessNumber. Sendiee uses the contact’s number or channel id. If that finds no chat, it falls back to the contact’s newest linked chat on that channel.
• phone, with optional channel (whatsapp by default, instagram or messenger) and businessNumber.

For phone:

• On WhatsApp, you may leave out businessNumber only when the account has exactly one WhatsApp number. Formatting in the phone number (+, spaces, dashes, brackets) is stripped.
• On Instagram and Messenger, businessNumber is required. It is your Instagram or Messenger account id, and phone is the customer’s Instagram or Messenger id.

This is the same targeting as the other Teambox endpoints, plus contactId. See Targeting a conversation.

Errors when finding the conversation

Add an Activity Entry

Writes one entry onto the conversation’s timeline. Call it when a call ends in your dialer, when a meeting is logged in your CRM, or when your system sends an email or SMS.

Code Example

curl -X POST "https://api.sendiee.com/v2.0/conversations/activity" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "phone": "919876543210",
    "type": "call",
    "title": "Outbound call · 4m 12s",
    "by": "Rahul Sharma",
    "note": "Interested in the 3BHK. Wants a site visit on Sunday morning.",
    "occurredAt": "2026-11-01T10:21:00+05:30",
    "linkUrl": "https://recordings.example.com/c/8f2a91",
    "linkLabel": "Call recording",
    "externalId": "call_8f2a91"
  }'

Response — 201 Created

{
  "success": true,
  "data": {
    "id": "6724a8e19d2b4e0011abc301",
    "conversationId": "66c3f0a19d2b4e0011ab9911",
    "type": "call",
    "title": "Outbound call · 4m 12s",
    "note": "Interested in the 3BHK. Wants a site visit on Sunday morning.",
    "by": "Rahul Sharma",
    "occurredAt": "2026-11-01T04:51:00.000Z",
    "linkUrl": "https://recordings.example.com/c/8f2a91",
    "linkLabel": "Call recording",
    "externalId": "call_8f2a91",
    "createdAt": "2026-11-01T04:55:42.310Z",
    "duplicate": false
  }
}

Retries and duplicates

Send an externalId with every entry, such as your call id. It is unique per account, not per chat. If the same externalId arrives again, Sendiee adds nothing and returns the first entry with duplicate: true and status 200. So you can retry a timed-out request, or replay a webhook from your dialer, without creating a second entry.

Errors

On top of the errors when finding the conversation:

Try It — Add an Entry

List Activity Entries

Returns a conversation’s activity entries, newest first. Only activity entries are returned. Assignment and status history come from Assignment History.

Code Example

curl -X GET "https://api.sendiee.com/v2.0/conversations/activity?phone=919876543210&limit=20" \
  -H "Authorization: Bearer YOUR_API_KEY"

Response — 200 OK

{
  "success": true,
  "data": {
    "conversationId": "66c3f0a19d2b4e0011ab9911",
    "activity": [
      {
        "id": "6724a8e19d2b4e0011abc301",
        "conversationId": "66c3f0a19d2b4e0011ab9911",
        "type": "call",
        "title": "Outbound call · 4m 12s",
        "note": "Interested in the 3BHK. Wants a site visit on Sunday morning.",
        "by": "Rahul Sharma",
        "occurredAt": "2026-11-01T04:51:00.000Z",
        "linkUrl": "https://recordings.example.com/c/8f2a91",
        "linkLabel": "Call recording",
        "externalId": "call_8f2a91",
        "createdAt": "2026-11-01T04:55:42.310Z"
      },
      {
        "id": "6721f0b29d2b4e0011abc2f4",
        "conversationId": "66c3f0a19d2b4e0011ab9911",
        "type": "email",
        "title": "Brochure emailed",
        "note": "",
        "by": "",
        "occurredAt": "2026-10-30T09:15:00.000Z",
        "linkUrl": null,
        "linkLabel": null,
        "externalId": null,
        "createdAt": "2026-10-30T09:15:03.884Z"
      }
    ],
    "hasMore": false,
    "nextBefore": null
  }
}

Entries have the same fields as the POST response, without duplicate. When hasMore is true, pass nextBefore as before to get the next page.

Errors

On top of the errors when finding the conversation:

Try It — List Entries

Delete an Activity Entry

Removes one activity entry. It disappears from open chats straight away. Only activity entries can be deleted. Assignment and status history can never be removed this way.

Code Example

curl -X DELETE "https://api.sendiee.com/v2.0/conversations/activity/6724a8e19d2b4e0011abc301" \
  -H "Authorization: Bearer YOUR_API_KEY"

Response — 200 OK

{
  "success": true,
  "data": {
    "id": "6724a8e19d2b4e0011abc301",
    "conversationId": "66c3f0a19d2b4e0011ab9911",
    "deleted": true
  }
}

Errors

Scopes and other errors

Adding and deleting entries need the activity:write scope. Listing needs activity:read. Keys with full access already have both. See API Key Scopes.

Errors use the envelope { "error": true, "code": "...", "message": "..." }.