---
title: "System Logs"
method: GET
path: "/v1.0/systemLogs"
tags: ["Lead System Logs"]
---

# System Logs

`GET /v1.0/systemLogs`

Returns system-event timeline entries for the lead, sorted by timelineTime descending (newest first), with offset-based pagination.

Only system / change-log activity events are returned (e.g. stage changes, assignment/routing, subscriptions, smart-plan tasks). Call, text, email and site-activity (search / view / favorite) entries are NOT included, nor is note content (e.g. adding a note); edit/delete-note actions (types 17/18) are included. Each entry includes both the `timelineType` integer and a human-readable `timelineTypeDesc` name, so you do not need to map the integer yourself.

Note: `startTime`/`endTime` query parameters are epoch milliseconds, but the `timelineTime`/`createTime`/`updateTime` fields in the response are ISO-8601 strings.

Authorization: the authenticated user must be the lead's owner or the shared agent; otherwise 403 is returned.

## Query parameters

- `leadId` integer, required
- `startTime` integer
- `endTime` integer
- `pageNumber` integer
- `pageSize` integer

## Headers

- `Authorization` string, required

## Response `200`

System log page retrieved successfully.

- SystemLogPageResponse — Paginated response wrapping the system log timeline entries.
  - `hasMore` 0 | 1 — Whether more pages exist after the current one. 1 = more entries, 0 = last page.
  - `timeLines` SystemLogResponse[] — Timeline entries on this page, sorted by timelineTime descending (newest first).
    - `id` string — Timeline record ID (returned as a string).
    - `leadId` integer — The id of the lead.
    - `agentId` integer — The id of the agent who triggered the event; 0 for system-generated events.
    - `timelineType` integer — The event type code. This endpoint only returns system / change-log activity types (it does not return call, text, email, note or site-activity entries). Use the companion `timelineTypeDesc` field for the human-readable name.
    - `timelineTypeDesc` string — The event name, derived from timelineType (e.g. "TeamStageChange" for 38). A stable enum identifier callers can switch on instead of mapping the integer themselves.
    - `timelineTime` string — When the event occurred (ISO-8601 with offset, UTC).
    - `createTime` string — When the entry was created (ISO-8601 with offset, UTC).
    - `updateTime` string — When the entry was last updated (ISO-8601 with offset, UTC).
    - `fromId` integer — The id of the FROM party. Meaning depends on timelineType (see reference).
    - `fromType` integer — The type of the FROM party: 0=Other, 1=Agent, 2=Lead, 3=Stage, 5=Lender, 6=LeadPond, 10=Property.
    - `toId` integer — The id of the TO party. Meaning depends on timelineType (see reference).
    - `toType` integer — The type of the TO party: 0=Other, 1=Agent, 2=Lead, 3=Stage, 5=Lender, 6=LeadPond, 10=Property.
    - `fromFirstName` string — The first name of the FROM party.
    - `fromLastName` string — The last name of the FROM party.
    - `toFirstName` string — The first name of the TO party.
    - `toLastName` string — The last name of the TO party.
    - `refId` integer — A business id referenced by this event (e.g. the task or routing record); 0 or -1 when not applicable.
    - `sticky` boolean — Whether this entry is pinned to the top of the timeline.
    - `canSticky` boolean — Whether the entry is eligible to be pinned.
    - `content` object — Event payload as a JSON object. Its structure varies by timelineType / timelineTypeDesc. For example, a stage change (38, "Lead Stage Change") carries `fromStageName`/`toStageName`; a smart-plan task (103) carries `taskType`/`taskContent`/`planName`.

## Other responses

- `400` — Invalid request parameters.
- `403` — The authenticated user does not have access to this lead.
- `500` — Internal server error.

---

[API](https://skmtc.net/lofty/apis/lofty-service-open-apis.md) · [All operations](https://skmtc.net/lofty/apis/lofty-service-open-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/lofty/lofty-service-open-apis/revisions/23e640467118/schema)