Skip to main content
POST
/
v1
/
person-activities
Create person activity
curl --request POST \
  --url https://api.stardex.ai/v1/person-activities \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "activity_type": "<string>",
  "activity_content": "<string>",
  "linkedin_url": "<string>",
  "email": "jsmith@example.com",
  "full_name": "<string>",
  "person_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
}
'
{
  "success": true,
  "data": {
    "id": "901e2345-e67f-89g0-h123-456789012345",
    "person_id": "123e4567-e89b-12d3-a456-426614174000",
    "activity_type": "meeting_note"
  }
}

Authorizations

​
Authorization
string
header
required

Authenticate with a Bearer token: API key, OAuth token, or session token.

Body

application/json
​
activity_type
string
required

Activity type key. Standard values: secondary_note (general note), meeting_note, meeting_transcript, email, interview_note, linkedin_message, text_message, candidate_summary, linkedin_message_response, call_note. Teams can also define custom activity types from Settings → Activity Types; discover the full list (including custom types) with GET /v1/person-activities/types.

Minimum string length: 1
​
activity_content
string
required

Activity body text. Stored as both HTML and plain text.

​
linkedin_url
string<uri>

LinkedIn profile URL to identify the person.

​
email
string<email>

Email address to identify the person.

​
full_name
string

Full name to identify the person. Least precise — prefer linkedin_url, email, or person_id.

​
person_id
string<uuid>

Person UUID (most precise). Get from POST /v1/persons/search or GET /v1/persons/{id}.

Response

Activity created

​
success
enum<boolean>
required
Available options:
true
​
data
object
required