> ## Documentation Index
> Fetch the complete documentation index at: https://docs.postsyncer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Put Back Account Posts

> After a reconnect, put the account back on the posts it was on before it was disconnected

## Put Back Account Posts

Disconnecting an account takes it off every post it was on. When the same profile is connected again to the same workspace (within 90 days), PostSyncer offers to put it back. [Get account](https://docs.postsyncer.com/api-reference/accounts/get.md) shows the offer in `posts_to_put_back`, and the workspace owner and admins get an `account.posts_to_put_back` [notification](https://docs.postsyncer.com/api-reference/webhooks/overview.md).

Nothing changes until someone chooses. Tell the user what `posts_to_put_back` says, and ask before you call this.

Putting back only adds the account to posts. Each post is handled on its own:

| What the post is now | What happens |
| - | - |
| A draft the disconnect moved from the schedule, unchanged since, its time more than 5 minutes ahead | The account is added and the post is scheduled again at the time it had (`scheduled_again`) |
| Scheduled or waiting for approval, its time more than 5 minutes ahead | The account is added; the post keeps its time (`added_to_scheduled`) |
| A draft | The account is added and it stays a draft (`added_to_draft`; `added_to_draft_time_passed` or `added_to_draft_changed` when the disconnect had unscheduled it but its time passed or it was edited since) |
| Published, failed, sending, deleted, or due within 5 minutes | Left as it is (`skipped_went_out`, `skipped_deleted`, `skipped_time_passed`) |

Nothing is published right away, and no post's text, media, time or other accounts change. The account's settings for each post (Pinterest board, TikTok privacy, YouTube title…) come back as they were. Calling it again does nothing more.

### Published posts come back on their own

Posts the account had already published don't need this call. Right after the reconnect, PostSyncer links them to the new account again with their link, numbers, day-by-day analytics and comments, as they were when the account was disconnected. `relinked` says how many. That sends nothing: no post, first comment, auto plug, comment reply or notification goes out, and the posts' status doesn't change. Comments written on the platform while the account was disconnected are read in later, but comment moderation doesn't act on them. A post that still has repeats to come is left out, so the account is not added to its next repeats.

### Request

**id** `integer` *required*

The reconnected account's ID.

**dismiss** `boolean`

`true` closes the offer and leaves every post as it is.

```bash theme={null}
curl -X POST "https://postsyncer.com/api/v1/accounts/123/put-back-posts" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
```

### Response

**message** `string`

What happened, in words.

**posts** `integer`

Posts the account was put back on.

**counts** `object`

Posts by what happened to them (see the table above). `added_to_draft_refused` counts posts kept in drafts because the plan's post limit refused scheduling them; `not_done` counts posts an error stopped. Those stay as they were, and calling again tries them again.

**relinked** `integer`

Published posts already linked to the account again, with their link, numbers and comments. That happens on its own at the reconnect.

**disconnected\_at** `string`

When the profile was disconnected.

**dismissed** `boolean`

`true` when you passed `dismiss`.

```json theme={null}
{
  "message": "The account is back on 6 posts.",
  "posts": 6,
  "counts": {
    "scheduled_again": 3,
    "added_to_scheduled": 1,
    "added_to_draft": 1,
    "added_to_draft_time_passed": 1,
    "added_to_draft_changed": 0,
    "added_to_draft_refused": 0,
    "skipped_deleted": 0,
    "skipped_already_there": 0,
    "skipped_went_out": 2,
    "skipped_time_passed": 0,
    "not_done": 0
  },
  "relinked": 14,
  "disconnected_at": "2026-11-10T09:30:00+00:00"
}
```

### Error Codes

**401** `Unauthorized`

Missing or invalid API token

**403** `Forbidden`

The key lacks `posts:update` or `posts:schedule`, or your workspace role may not publish

**404** `Not Found`

No account with this ID in a workspace you can access

**409** `Conflict`

These posts are being put back already. Try again in a moment.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.