Skip to main content
POST
/
v1
/
activities
Create activity
curl --request POST \
  --url https://api.clientcommander.com/v1/activities \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "personId": "<string>",
  "channel": "<string>",
  "content": "<string>"
}
'
{
  "meta": {
    "requestId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "timestamp": "2023-11-07T05:31:56Z",
    "version": "1.0.0"
  },
  "data": {
    "id": "<string>",
    "personId": "<string>",
    "createdAt": "2023-11-07T05:31:56Z",
    "channel": "<string>",
    "content": "<string>",
    "agentName": "<string>",
    "starred": false
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.clientcommander.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

Authorization
string
header
required

API key for authentication using Bearer token scheme.

How to get your API key:

  1. Log into Client Commander
  2. Go to Admin > API Keys
  3. Click Create API Key
  4. Copy the key and use it in the Authorization header:
Authorization: Bearer ccmd_live_your_key_here

Body

application/json
personId
string
required
type
enum<string>
required
Available options:
call,
email,
note,
meeting,
sms,
activity
channel
string
direction
enum<string>
Available options:
inbound,
outbound
content
string
Maximum string length: 5000

Response

201 - application/json

Activity created

meta
object
required
data
object