---
title: "Get activities for a contact"
method: GET
path: "/v3/contacts/{id}/activities"
tags: ["Contacts"]
---

# Get activities for a contact

`GET /v3/contacts/{id}/activities`

<small>_Requires the `contacts:read` scope (or a broader one that includes it)._</small>

Use this endpoint when you need a contact's activity history — the emails, calls, status changes, and other tracked events recorded on its timeline. Results are paged with the top and skip query parameters.

## Path parameters

- `id` integer, required

## Query parameters

- `top` integer
- `skip` integer

## Response `200`

Contact activities retrieved successfully

- object
  - `items` object[]
    - `id` integer
    - `date` string, date-time
    - `activityType` string
    - `sourceType` string
    - `userName` string, nullable
    - `userId` integer
    - `content` object, nullable
  - `hasMore` boolean

## Other responses

- `400` — Route-parameter validation failure (e.g. non-positive `id`) or a business rule rejection.
- `401` — Unauthorized. The response body is empty; check the `WWW-Authenticate` header for the expected scheme.
- `403` — User lacks required feature scope to view this contact
- `404` — Contact not found
- `429` — Too Many Requests

---

[API](https://skmtc.net/reply/apis/reply-api.md) · [All operations](https://skmtc.net/reply/apis/reply-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/reply/reply-api/revisions/1c3d32eaf95e/schema)