> For the complete documentation index, see [llms.txt](https://help.blotato.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blotato.com/api-and-mcp-concepts/scheduling.md).

# Scheduling

Resolve UTC times and destination slots, verify the scheduled result, and edit or cancel the existing item.

Choose a specific publish time or the next free calendar slot, not both. An explicit `scheduledTime` does not bypass slot validation if `useNextFreeSlot` is also `true`. A scheduled result confirms the queue entry. Check publication after the chosen time if your workflow needs the live post URL.

## Choose a time

1. Resolve the user's date, time, and timezone. Ask for the timezone when it is unknown.
2. Convert the chosen instant to a future UTC ISO 8601 timestamp, such as `2030-06-15T15:00:00Z`. Replace example dates with the intended future date.
3. Set `scheduledTime` in the create-post request.
4. Read the returned `scheduledTime` and report it in the user's timezone.

For MCP, `scheduledTime` is a tool argument. For REST, it is a top-level sibling of `post`:

```json
{
  "post": {
    "accountId": "ACCOUNT_ID_FROM_LOOKUP",
    "content": {
      "platform": "twitter",
      "text": "Scheduled post example",
      "mediaUrls": []
    },
    "target": { "targetType": "twitter" }
  },
  "scheduledTime": "2030-06-15T15:00:00Z"
}
```

The API parses and returns scheduled times in UTC. There is no separate timezone field in this create-post request. The web calendar's [timezone setting](/web-app-features/content-calendar/timezone.md) controls the calendar experience.

## Use the next free slot

1. Set up the calendar's [schedule slots](/web-app-features/content-calendar/create-schedule.md).
2. Set `useNextFreeSlot: true` in place of a specific `scheduledTime`.
3. Report the resolved time returned by Blotato.

If no matching slot or available time is found, post creation returns a validation error. Add or correct slots for the intended platform, account, and Page. Do not retry without scheduling fields unless the user authorizes immediate publishing.

In REST, `useNextFreeSlot` is a top-level sibling of `post`. For slot definitions and advanced REST scheduling, see [Weekly posting schedule](/rest-api-reference/schedule-slots.md) and [Publish Post](/rest-api-reference/publish-post.md).

## Edit or cancel a scheduled post

1. List schedules with `blotato_list_schedules` or `GET /v2/schedules`.
2. Read the selected scheduled post with `blotato_get_schedule` or `GET /v2/schedules/:id`.
3. Update it with `blotato_update_schedule` or `PATCH /v2/schedules/:id`, or cancel it with `blotato_delete_schedule` or `DELETE /v2/schedules/:id`.
4. Check the returned state or re-read the schedule to verify the change.

Use the scheduled post's ID from the schedule listing. See [Scheduled Posts](/rest-api-reference/schedules.md) for update fields and preserved content.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.blotato.com/api-and-mcp-concepts/scheduling.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.