# Scheduling posts

Add `scheduled_at` with the date, time and **time zone** (ISO 8601 format). Without that field, the post goes out right away.

```
curl -X POST https://wyroapi.com/v1/posts \
  -H "Authorization: Bearer $WYRO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text":"We open Saturday at 9","platforms":["instagram","facebook"],"media":[{"url":"https://picsum.photos/seed/abre/1080/1080"}],"scheduled_at":"2026-11-07T09:00:00-03:00"}'
```

The response includes `"status": "scheduled"`. Check the status with `GET /v1/posts/{id}`: it changes to `published` (or `failed`, with the reason per network) when the time comes.

## Time zone

Always include the offset: `+00:00` for UTC, `-03:00` for Buenos Aires or São Paulo, `-06:00` for Mexico City, `-05:00` for Bogotá and Lima. A date without a time zone is rejected with `validation_error`.

## From the MCP

Ask your agent: *"Schedule it for Monday at 10 a.m. Buenos Aires time"*. The `wyro_publicar` tool uses the `programar_para` field.

## From the CLI

```
npx @wyroapi/wyro publicar "We open Saturday" --red instagram --medio https://… --programar 2026-11-07T09:00:00-03:00
```
