---
title: "List extension contact changes"
method: POST
path: "/user/extension_contacts/sync_tokens/{token}/diff"
tags: ["User"]
---

# List extension contact changes

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

List extension contact 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.
    - `display_name` string — The display name of user.
    - `email` string — The email address.
    - `mobile_phone` string — The email address.
    - `work_phone` string — The email address.
    - `home_phone` string — The email address.
    - `address` string — The address.
    - `department` string — The department of user.
    - `avatar_file_url` string — The relative path to file url for file downloading.
    - `extension_number` string — The extension number.
    - `favorite` boolean — Mark if a contact has been added to the favorites list.
    - `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.

## 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)