Get Contact Activity

Paginated activity feed for a specific contact — notes created, messages sent, property likes, saved searches, and more. Separate endpoint for performance since activity data can be large.

GET/v1/contacts/:contactId/activity

Authentication

OAuthAuthorization: Bearer

Requires OAuth access token (scope: contacts)

Query Parameters

contactIdstring

required

Contact ID (URL path parameter)

pagenumber

optional

Page number (default: 1)

limitnumber

optional

Results per page (max 50, default: 20)

typesstring

optional

Comma-separated activity types to filter (e.g., NOTE_CREATED,MESSAGE_SENT)

sincestring

optional

ISO 8601 timestamp. Only activities after this date

Responses

200Success

application/json

totalnumber

Total matching activities

pagenumber

Current page number

limitnumber

Results per page

activityarray

Array of activity objects

Select a contact and activity window

Replace contactId in the URL path with a contact identifier from the contacts API. Use a token with the contacts scope. The activity feed is separate from the contact record, so request it when your application needs the timeline for a specific person. This keeps a basic contact view from depending on a potentially larger activity history.

Filter and paginate the feed

Use types for a comma-separated set of activity types and since for an ISO 8601 date filter. The page and limit parameters control pagination; the documented maximum limit is 50. Read total, page and limit alongside the activity array when building navigation. Keep filters consistent across pages and avoid treating a filtered empty feed as proof that the contact has never interacted.

Interpret each event

Each activity includes a type and creation time, with actor, target and data fields describing its context. Read the event type before interpreting data because payloads differ by activity. Present dates in the timezone appropriate to your users and distinguish messages, notes and property interactions. Use event identifiers to avoid duplicate timeline entries when reloading or merging pages, and keep personal activity details out of public logs.

OAuth authorization · Check the connected account · API setup guide

Request

curl --request GET \
  --url "https://api.pandaidx.com/v1/contacts/507f1f77bcf86cd799439011/activity?limit=10" \
  --header "Authorization: Bearer YOUR_ACCESS_TOKEN"

Response200 OK

{
  "total": 45,
  "page": 1,
  "limit": 20,
  "activity": [
    {
      "id": "507f1f77bcf86cd799439099",
      "type": "NOTE_CREATED",
      "actor": {
        "type": "user",
        "name": "John Smith"
      },
      "target": {
        "type": "contact",
        "name": "Maria Garcia"
      },
      "data": "Object",
      "createdAt": "2026-03-18T14:30:00Z"
    }
  ]
}