# Disconnect a social account

> Markdown version of https://docs.postlake.dev/api/delete-social-accounts-by-id . The canonical page for humans.
> PostLake is the social media API for AI agents: https://postlake.dev/llms.txt

`DELETE /v1/social-accounts/{id}`

Disconnect at the owner's request. Published posts stay untouched. scheduledPosts=keep (default) preserves schedules and stable identity for reconnection. remove removes this destination from scheduled posts; posts with no destinations left become drafts with their content preserved. remove requires expectedSnapshot from disconnect-preview. Confirmation is fenced against full-post edits, new affected schedules and publishing claims in one bounded transaction. Provider revocation is best effort after the guarded local transaction. Maximum 100 schedules; larger selections require bulk destination edits first. No credits are charged.

## Request

Authenticate with a bearer API key. Agents calling over MCP authorise with OAuth instead and never handle the key.

```bash
curl -X DELETE https://api.postlake.dev/v1/social-accounts/{id} \
  -H "Authorization: Bearer $POSTLAKE_API_KEY"
```

### Parameters

| Field | Type | Required | What it is |
| --- | --- | --- | --- |
| `id` | string | Yes | In the URL. |
| `scheduledPosts` | string | No | Query string. |
| `expectedSnapshot` | string | No | Query string. Full-state snapshot from disconnect-preview. Required for remove. |


## Response

Disconnected (`200`).

| Field | Type | Required | What it is |
| --- | --- | --- | --- |
| `id` | string | Yes |  |
| `disconnected` | boolean | Yes |  |
| `platform` | string | Yes |  |
| `handle` | string | Yes |  |
| `profileId` | string | No |  |



### Example

```json
{
  "id": "…",
  "disconnected": false,
  "platform": "…",
  "handle": "…",
  "profileId": "…"
}
```


## Calling this from an agent

Agents do not call REST. They call tools. Over the hosted MCP server this operation is `list_social_accounts`, and the agent authorises with OAuth so your API key is never pasted into a chat or seen by the model. You control what any one agent may do: which brands it may act for, which networks it may reach, how much a day, and whether it may spend credits bought up front.

## Errors

Every failure uses one shape: a stable `type`, a granular `code`, the field at fault in `param`, and a plain-language `fix`. See https://docs.postlake.dev/errors.md .

Check the result before retrying a write. Only operations that explicitly support idempotency can safely replay an `Idempotency-Key`.

## Common questions

**Can an AI agent do this without the REST API?**

Yes. Over MCP the same job is the list_social_accounts tool. The agent authorises with OAuth, so no API key is pasted into a chat or seen by the model, and the answer comes back in the same normalised shape.

**Is it safe to retry this call?**

Do not automatically repeat a write after a timeout unless that endpoint explicitly documents idempotency. First read the resulting state; a second request could repeat the action.

**What happens when it fails?**

You get one error shape: a stable type, a granular code you can branch on, the offending field in param, and a fix written so an agent can correct itself rather than stop. Full list on Errors and retries.

## Related

- [List social accounts](https://docs.postlake.dev/api/get-social-accounts.md) `GET /v1/social-accounts`
- [Retrieve a social account](https://docs.postlake.dev/api/get-social-accounts-by-id.md) `GET /v1/social-accounts/{id}`
- [Preview channel disconnect](https://docs.postlake.dev/api/get-social-accounts-by-id-disconnect-preview.md) `GET /v1/social-accounts/{id}/disconnect-preview`
- [Search Facebook Pages for a mention](https://docs.postlake.dev/api/get-social-accounts-by-id-facebook-pages-search.md) `GET /v1/social-accounts/{id}/facebook-pages/search`