---
title: "Log activities for a contact"
method: POST
path: "/contacts/{id}/activities"
tags: ["contacts"]
---

# Log activities for a contact

`POST /contacts/{id}/activities`

Log one or more activities (e.g. message_sent, profile_visited, post_liked) for a contact. Max 100 per request..

## Path parameters

- `id` string, required

## Request body

- object
  - `activities` object[], required — Activities to log
    - `type` 'connection_request' | 'message' | 'connection_accepted' | 'profile_view' | 'engagement_observed' | 'post_interaction' | 'search_found' | 'qualification' | 'stage_change' | 'user_interest' | 'meeting_booked' | 'meeting_completed' | 'meeting_cancelled' | 'do_not_contact', required — Activity type
    - `content` string — Human-readable description of what happened
    - `metadata` unknown

## Response `200`

Activities logged

- object
  - `success` true, required
  - `created` integer, required
  - `creditsUsed` integer, required — Credits consumed by this call (always 0 for contacts queries).
  - `retryAfter` integer, required — Seconds to wait before next call of the same type (always 0 for contacts queries).

## Other responses

- `400` — The server cannot or will not process the request due to something that is perceived to be a client error.
- `401` — Although HTTP specifies "unauthorized", this response means "unauthenticated". Authenticate to continue. NOTE: 401 is also returned with code "linkedin_not_connected" when the caller IS authenticated but has no connected LinkedIn account — connect LinkedIn (not re-authenticate) to continue.
- `403` — The client does not have access rights to the content.
- `404` — The server cannot find the requested resource.
- `409` — The request conflicts with the current state of the server.
- `410` — The requested content has been permanently deleted from the server.
- `422` — The request was well-formed but was unable to be followed due to semantic errors.
- `429` — Rate limit exceeded. Read error.retryAfter for the wait time in seconds.
- `500` — The server encountered a situation it does not know how to handle.
- `502` — LinkedIn returned a server error or the proxy connection failed. Retry after a few seconds.
- `503` — Proxy capacity temporarily exceeded. Retry after a few seconds.

---

[API](https://skmtc.net/berea/apis/bereach-api.md) · [All operations](https://skmtc.net/berea/apis/bereach-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/berea/bereach-api/versions/3caf12036b26/schema)