# Create a scheduled event

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

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

Create an event on the account, where the network allows it through the API. Instagram calls this a reminder and normally expects it to be added while composing a post in the app; this asks the API directly, and a network that refuses says so in its own words. The returned id goes in the `upcomingEventId` post option.

## 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}/events \
  -H "Authorization: Bearer $POSTLAKE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"title":"…","startsAt":"…","endsAt":"…"}'
```

### Parameters

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

### Body

| Field | Type | Required | What it is |
| --- | --- | --- | --- |
| `title` | string | Yes |  |
| `startsAt` | string | Yes |  |
| `endsAt` | string | No |  |


## Response

Created (`201`).

| Field | Type | Required | What it is |
| --- | --- | --- | --- |
| `id` | string | Yes |  |
| `title` | string | Yes |  |
| `startsAt` | string | No |  |
| `endsAt` | string | No |  |



### Example

```json
{
  "id": "…",
  "title": "…",
  "startsAt": "…",
  "endsAt": "…"
}
```


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

- [Ad account lookup (deferred)](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`
- [Facebook branded-content posts (deferred)](https://docs.postlake.dev/api/get-social-accounts-by-id-branded-content-posts.md) `GET /v1/social-accounts/{id}/branded-content-posts`
- [Branded partner lookup (deferred)](https://docs.postlake.dev/api/get-social-accounts-by-id-branded-partners.md) `GET /v1/social-accounts/{id}/branded-partners`