Account status updates

Learn how to handle account status.

Feature available for: LinkedIn, WhatsApp, Instagram, Messenger, Telegram, X (Twitter), Google, Microsoft, IMAP.

postpress's Account Status Webhook is a powerful feature that allows you to monitor the life cycle of an account's status and take actions based on changes in the status. This Webhook provides real-time updates on the synchronization status of your accounts, and on the connection creation.

Synchronization status

Here is an example payload for a synchronization request:

{
  "AccountStatus": {
    "account_id": "h_EKCy2lRLef5NzHp0iw4A",
    "account_type": "LINKEDIN",
    "message": "CREDENTIALS"
  }
}

Below are the different synchronization statuses that can be notified by the Webhook.

StatusDescription
OK

Everything seems to be in good order.

When the account status is not OK:

  • You can still retrieve any data (chats, messages, and so on) using GET methods, but this data is no longer guaranteed to be up to date with the messaging provider.
  • You will no longer receive updates on new messages through Webhooks.
ERROR / STOPPEDAccount synchronization has stopped due to an unexpected error during data fetching.
CREDENTIALS

Synchronization of the account has been interrupted due to invalid or missing credentials required for retrieving new data. This situation may arise in several scenarios, including, but not limited to:

IMAP

  • User updates their provider's password.

Email (Google / Microsoft)

  • User revokes your application's authorization from their account center.
  • Admin of the user revokes permissions of the app or current tokens for security reasons.
  • User changes their credentials and checks the option to revoke current tokens.
  • Account does not exist anymore, or the configured email changed.
  • OAuth keys changed in your settings.
  • Not enough scopes were checked by the end user.

WhatsApp / Telegram

  • User terminates the session via the app settings.
  • Excessive requests to sensitive endpoints (such as fetching profiles or sending messages without a good answer rate, or high report rate by users) can cause temporary or definitive restrictions.
  • Phone has no network for a long period.

Instagram

  • Instagram asks for a security checkpoint you need to validate in the UI before reconnecting.
  • The session expires after one year.
  • User terminates the session via the preference settings.
  • User changes their credentials and checks the option to revoke current tokens.
  • Excessive, repetitive, or non-randomized requests to sensitive endpoints (such as fetching profiles or lists of relations every day at the same hour) may trigger automation warnings and result in the account being disconnected. See the provider limits and restrictions page for recommendations.
  • Your proxy is too slow or down for an extended period.

LinkedIn

  • The session expires after one year.
  • User terminates the session via the preference settings.
  • User changes their credentials and checks the option to revoke current tokens, or activates 2FA.
  • Excessive, repetitive, or non-randomized requests to sensitive endpoints (such as fetching profiles or lists of relations every day at the same hour) may trigger automation warnings and result in the account being disconnected. See the provider limits and restrictions page for recommendations.
  • Too many requests with reject codes (invalid_attendee, insufficient_credit, and so on). You need to handle error codes and stop or adapt the sequence.
  • Users may be prompted to select a session (only with Recruiter accounts connected with credentials. Use the cookies method to bypass this).
  • When connected with cookies: user logs out in their browser (for example to switch account).
  • When connected with cookies and custom auth: providing an incorrect user agent. You need to provide the user_agent field. The LinkedIn account of the user will also be disconnected quickly in their browser.
  • When connected with cookies and hosted auth: collecting the cookie in another browser or pasting a cookie from another user. The LinkedIn account of the user will be disconnected quickly in their browser too.
  • Your proxy is too slow or down for an extended period.
CONNECTINGThe account is attempting to connect. If your credentials are correct, it may be because the provider is temporarily down, your proxy is unavailable, or a synchronization catch-up is in progress. This is a temporary status.
DELETEDYou deleted the account.
CREATION_SUCCESSThe account was successfully added and the initial data synchronization has begun. CREATION_SUCCESS can be notified by the Webhook and / or notify_url in hosted auth (not with the same format). The account can take a few seconds to be able to perform requests. You can wait for the OK status to be sure everything is ready.
RECONNECTEDAccount has been reconnected successfully. Can be notified by the Webhook and / or notify_url in hosted auth (not with the same format).
SYNC_SUCCESSOnly for LinkedIn / IMAP / WhatsApp / Instagram / Telegram. The account (re)synchronization is finished. For LinkedIn accounts with a premium option (Recruiter or Sales Navigator), you will receive two payloads: one for Classic and another for the premium option. These can be identified under product.
Updated May 2026