# Subscribe this channel to webhooks

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

`POST /v1/social-accounts/{id}/webhook`

Some networks need the subscription on the ACCOUNT as well as the app. Facebook is the case: subscribing the app is not enough, the Page has to be subscribed too or nothing is ever delivered, however well the callback is configured. Defaults to feed, mention and messages.

## Request

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

```bash
curl -X POST https://api.postlake.dev/v1/social-accounts/{id}/webhook \
  -H "Authorization: Bearer $POSTLAKE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"fields":["…"]}'
```

### Parameters

| Field | Type | Required | What it is |
| --- | --- | --- | --- |
| `id` | string | Yes | In the URL. |

### Body

| Field | Type | Required | What it is |
| --- | --- | --- | --- |
| `fields` | array of string | No | Which events to subscribe to. Defaults to feed, mention, messages. |


## Response

Subscribed (`200`).

| Field | Type | Required | What it is |
| --- | --- | --- | --- |
| `subscribed` | boolean | Yes |  |
| `fields` | array of string | Yes |  |



### Example

```json
{
  "subscribed": false,
  "fields": [
    "…"
  ]
}
```


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

Retries are safe: send the same `Idempotency-Key` and a call that already succeeded returns its original result rather than repeating it.

## 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?**

Yes. Send the same Idempotency-Key and a call that already succeeded returns its original result instead of repeating the work. That is what makes it safe to hand to an agent that retries on its own.

**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

- [Ad accounts this channel can use](https://docs.postlake.dev/api/get-social-accounts-by-id-ad-accounts.md) `GET /v1/social-accounts/{id}/ad-accounts`
- [Publishing headroom left](https://docs.postlake.dev/api/get-social-accounts-by-id-allowance.md) `GET /v1/social-accounts/{id}/allowance`
- [Branded content partners](https://docs.postlake.dev/api/get-social-accounts-by-id-branded-partners.md) `GET /v1/social-accounts/{id}/branded-partners`
- [Scheduled events on this channel](https://docs.postlake.dev/api/get-social-accounts-by-id-events.md) `GET /v1/social-accounts/{id}/events`