---
title: "Resynchronize account messaging data"
method: GET
path: "/api/v1/accounts/{account_id}/sync"
tags: ["Accounts"]
---

# Resynchronize account messaging data

`GET /api/v1/accounts/{account_id}/sync`

This route can be used both to initiate a sync process (from scratch or within a specific time span) and to monitor its status via regular polling. Supported providers: LinkedIn and Telegram. Instagram and WhatsApp are not supported by this route.

## Path parameters

- `account_id` string, required

## Query parameters

- `chunk_size` number
- `partial` boolean
- `linkedin_product` 'classic' | 'recruiter' | 'sales_navigator'
- `before` number
- `after` number

## Response `200`

OK. Request succeeded.

- object
  - `object` 'AccountResync', required
  - `status` 'SYNC_STARTED' | 'SYNC_RUNNING' | 'SYNC_DONE' | 'SYNC_ERROR' | 'CHUNK_DONE', required — The status of the synchronization. You can setup a regular polling on the same route to get updates on its status. A new request after a SYNC_DONE, CHUNK_DONE or SYNC_ERROR response will start a fresh sync.

## Other responses

- `400` — ## Bad Request ### Invalid parameters - Type: "errors/invalid_parameters" One or more request parameters are invalid or missing. ### Missing parameters - Type: "errors/missing_parameters" One or more request parameters are missing. ### Invalid parameters - Type: "errors/invalid_request" One or a combination of request parameters are invalid. ### Malformed request - Type: "errors/malformed_request" The given request has been rejected by the provider. ### Content too large - Type: "errors/content_too_large" The request payload or filter query is too large and has been rejected by the provider. ### Too many characters - Type: "errors/too_many_characters" The provided content exceeds the character limit. ### Unescaped characters - Type: "errors/unescaped_characters" The request path contains unescaped characters. ### Limit too high - Type: "errors/limit_too_high" Provider cannot accept such high pagination limit. See API reference for details. ### Invalid action - Type: "errors/invalid_action" This action is invalid. ### Invalid label - Type: "errors/invalid_label" This label is invalid.
- `401` — ## Unauthorized ### Disconnected account The account appears to be disconnected from the provider service. undefined
- `403` — ## Forbidden ### Feature not subscribed The requested feature has either not been subscribed or not been authenticated properly. undefined
- `404` — ## Not Found ### Resource not found. The requested resource were not found. Account not found
- `500` — ## Internal Server Error ### Unexpected error - Type: "errors/unexpected_error" Something went wrong. {{moreDetails}} ### Provider error - Type: "errors/provider_error" The provider is experiencing operational problems. Please try again later. ### Authentication intent error - Type: "errors/authentication_intent_error" The current authentication intent was killed after failure. Please start the process again from the beginning.
- `501` — ## Not Implemented ### Missing feature Requested feature is planned but has not been implemented yet. undefined
- `503` — ## Service Unavailable ### No client session - Type: "errors/no_client_session" No client session is currently running. ### No channel - Type: "errors/no_channel" No channel to client session. ### Handler missing - Type: "errors/no_handler" Handler missing for that request. ### Network down - Type: "errors/network_down" Network is down on server side. Please wait a moment and retry. ### Service unavailable - Type: "errors/service_unavailable" Please try again later.
- `504` — ## Gateway Timeout ### Request timed out - Type: "errors/request_timeout" Request Timeout. Please try again, and if the issue persists, contact support.

---

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