Log an outreach activity
Record that a teammate reached out to this person: an email, a DM, a call. The first activity claims an unowned person for whoever reached out and moves not_contacted to contacted; an existing owner and a later stage are kept. `memberId` defaults to the signed-in member; an API key that omits it logs an unattributed activity, which claims nobody.
API key minted via POST /v1/api-keys (format mk_live_...)
In: header
Path Parameters
Person id (aut_...).
1 <= lengthHow they were reached: email, x, linkedin, bluesky, reddit, github, call, meeting or other.
"email" | "x" | "linkedin" | "bluesky" | "reddit" | "github" | "call" | "meeting" | "other"What was sent or said, briefly.
""length <= 2000When the contact happened (ISO 8601, or epoch ms). Defaults to now.
date-timeThe member who reached out (user id). Defaults to the signed-in member; an API key that omits it logs an unattributed activity.
1 <= lengthResponse Body
application/json
application/json
application/json
application/json
curl -X POST "https://api.mentio.dev/v1/people/aut_abc123/activities" \ -H "Content-Type: application/json" \ -d '{ "channel": "email" }'{
"id": "string",
"personId": "string",
"channel": "email",
"note": "string",
"member": {
"id": "string",
"name": "string",
"email": "string"
},
"occurredAt": "string",
"createdAt": "string"
}{
"error": {
"code": "unauthorized",
"message": "string",
"requestId": "string",
"retryAfterSeconds": 0
}
}{
"error": {
"code": "unauthorized",
"message": "string",
"requestId": "string",
"retryAfterSeconds": 0
}
}{
"error": {
"code": "unauthorized",
"message": "string",
"requestId": "string",
"retryAfterSeconds": 0
}
}List outreach activities GET
Every logged contact with this person across all their accounts, newest first (at most 200): who reached out, the channel, when, and a short note. Read it before reaching out so two teammates never contact the same person without knowing.
Merge an account into a person POST
Declare that this account and another person are the same human, for your workspace only. Their mentions, tags, notes and outreach activities combine under the person named by `into`, which keeps its owner and stage unless it had none.