AI agent schedule tweets API: generate, schedule, and review posts
An AI agent schedule tweets API workflow lets an agent generate content, choose publish times, and send each post through a single scheduling request instead of requiring custom publishing infrastructure for every account. The example in this guide connects an AI agent Twitter account workflow to a Twitter posting API, sets publishNow to false, and supplies scheduledFor and timezone so the post can be reviewed before it goes live. It also shows how to schedule tweets across time zones, attach an image conditionally, and review scheduled posts before publishing.
What the example does and does not prove
The premise is simple: an agent generates a batch of posts, picks publish times spread across the day, and sends each one through the same scheduling endpoint. In the source example the agent generated five posts per day and spread them across US time zones, while the request itself carried a single timezone value, Asia/Jerusalem, alongside the scheduledFor timestamp. That distinction matters when you reproduce the workflow: the spread of slots is a planning decision made by the agent, while scheduledFor and timezone are the fields that tell the API when to publish. Treat the five-post cadence as an example pattern, not a requirement of the endpoint. The endpoint contract shown here accepts one post per request, with one platform target in the example.
Exact request contract and field map
The request uses POST with a JSON body and two headers. The x-access-key header carries the API key, and Content-Type is set to application/json. Inside the body, content holds the post text, platforms is an array containing a single target object, and that target sets platform to twitter and accountId to the identifier for the connected account. publishNow is false in the scheduling example, which signals that the post should not publish immediately. scheduledFor supplies the planned publish time and timezone supplies the timezone context for that time. When an image is available, the agent adds mediaItems with an entry whose type is image and whose url is the image URL. The full field map and the worked example are provided in the tables and code example below, titled Input contract for POST /v1/posts and Agent scheduling example for POST /v1/posts.
What content the agent generates
Content generation is separate from scheduling. The agent first produces the text for each post, then decides on a time slot, then builds the request body and sends it. In the source example the generated posts were about the agent workflow itself, including the tools used for posting and for building the agent. You can apply the same separation to any topic: generate and store the content first, assign each item a scheduledFor value, and only then call the API. Keeping generation and scheduling as separate steps makes it easier to review the queue, because a content problem can be fixed without changing the publish plan, and a timing problem can be fixed without regenerating the text.
Review, edit, and cancel before publishing
Scheduling with publishNow set to false creates a window for human oversight. The source workflow included a summary of what had been scheduled, followed by the ability to review scheduled posts in a dashboard, edit content, change times, or cancel a post before it went live. The posts view showed content, platform, and exact publish time for each scheduled item. Reproduce that oversight loop in your own setup even if your interface differs: list every scheduled post with its content, target account, and publish time; allow edits to content and time; and allow cancellation before the scheduled moment. The failure and review matrix below, titled Failure and review matrix, lists the checks to run before a scheduled post is allowed to publish.
Choosing Embeddable, Claude Code, n8n, or custom HTTP
Because the mechanism is a REST API, the agent framework is interchangeable. Embeddable suits a visual agent builder approach, Claude Code suits building an agent that posts from a terminal, n8n suits connecting the API as a webhook node inside automation flows, and custom code suits direct HTTP control with an API key. Choose based on how you want to build and operate the agent: visual building, terminal use, automation flows, or direct HTTP control. In every case the scheduling request stays the same, so switching frameworks should not require changing the post contract. The comparison criteria are summarized in the table titled Choosing an agent framework.
Failure matrix and pre-publish checklist
Before relying on an automated queue, run a pre-publish checklist against every request. Confirm that accountId matches the intended connected account, that scheduledFor and timezone are both present when publishNow is false, that publishNow is not accidentally set to true for a post meant to be reviewed, and that mediaItems is included only when an image URL exists. After scheduling, confirm that each post appears in the review list with the correct content, platform, and publish time, and that edit and cancel actions work before the scheduled moment. If any check fails, fix the request or the queue item rather than publishing and correcting afterward.
| Field | Location | Example value | Required or conditional |
|---|---|---|---|
| content | Body | post.content | Present in example |
| platforms | Body | Array with one target object | Present in example |
| platform | Body, inside platforms[] | 'twitter' | Present in example |
| accountId | Body, inside platforms[] | TWITTER_ACCOUNT_ID | Present in example |
| publishNow | Body | false | Present in example; false means scheduled, not immediate |
| scheduledFor | Body | scheduledFor | Present in example for scheduled publishing |
| timezone | Body | 'Asia/Jerusalem' | Present in example |
| mediaItems | Body | [{ type: 'image', url: post.imageUrl }] | Conditional: only when post.imageUrl is present |
| type | Body, inside mediaItems[] | 'image' | Conditional with mediaItems |
| url | Body, inside mediaItems[] | post.imageUrl | Conditional with mediaItems |
| x-access-key | Header | API_KEY | Present in example |
| Content-Type | Header | 'application/json' | Present in example |
Field presence and values are taken from the source request example; response and error contracts were not supplied.
| Framework | Best fit | Decision criteria |
|---|---|---|
| Embeddable | Visual agent builder | Choose when you want to build the agent visually rather than in code |
| Claude Code | Terminal-based agent | Choose when you want to build an agent that posts from your terminal |
| n8n | Automation flows | Choose when you want the API as a webhook node inside automation flows |
| Custom HTTP code | Direct API calls | Choose when you want direct HTTP control with an API key |
Comparison is based on the roles described in the source; no framework is endorsed.
| Failure or risk | Check | Action before publishing |
|---|---|---|
| Wrong accountId | Confirm accountId matches the intended connected account | Correct the target or cancel the scheduled post |
| Missing scheduledFor or timezone | Confirm both are present when publishNow is false | Add the missing field before the post is scheduled |
| publishNow true instead of false | Confirm publishNow is false for posts meant to be reviewed | Reschedule with publishNow false if review is required |
| Missing mediaItems | Confirm mediaItems is present only when an image URL exists | Add mediaItems with type image and url, or remove the image expectation |
| Post needs changes after scheduling | Review scheduled posts for content, platform, and publish time | Edit content or time, or cancel before the scheduled moment |
Checks are derived from the example fields and the review workflow; no error contract was supplied.