---
title: "List personal cdr changes"
method: POST
path: "/user/cdrs/sync_tokens/{token}/diff"
tags: ["User"]
---

# List personal cdr changes

`POST /user/cdrs/sync_tokens/{token}/diff`

List personal cdr changes.

## Path parameters

- `token` string, required — The sync token. Clients should treat the sync token as an opaque string and should never try to assemble it. This document imposes no constraints on the format and clients should never impose any.

## Response `200`

OK

- object
  - `token` string — The sync token. Clients should treat the sync token as an opaque string and should never try to assemble it. This document imposes no constraints on the format and clients should never impose any.
  - `items` object[]
    - `id` string — The unique ID of the resource.
    - `change_type` 'CREATED' | 'UPDATED' | 'DELETED' — The resource change types can be either: - `CREATED`: The resource has been created. - `UPDATED`: The resource has been updated. - `DELETED`: The resource has been deleted.
    - `items` object[]
      - `caller` string — The caller number of the call.
      - `callee` string — The callee number of the call.
      - `started_at` string, date_time — The RFC 3339 format is defined by The date_time notation as defined by [RFC 3339, section 5.6](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6), for example, 2017-07-21T17:32:28Z
      - `answered_at` string, date_time — The RFC 3339 format is defined by The date_time notation as defined by [RFC 3339, section 5.6](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6), for example, 2017-07-21T17:32:28Z
      - `ended_at` string, date_time — The RFC 3339 format is defined by The date_time notation as defined by [RFC 3339, section 5.6](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6), for example, 2017-07-21T17:32:28Z
      - `outbound_caller_id` string — Outbound caller id.
      - `did_cid` string — The DID CID of CDR.
      - `trunk` string — The trunk name of CDR.

## Other responses

- `4XX` — Error

---

[API](https://skmtc.net/portsip/apis/portsip-pbx-rest-api.md) · [All operations](https://skmtc.net/portsip/apis/portsip-pbx-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/portsip/portsip-pbx-rest-api/revisions/577415d4a3d5/schema)