programmatic scheduling for custom workflows
how TTP supports validated content submission, approval, and timed publication through agent-driven automation and a single approval queue
what this page covers
this page explains how to submit validated content and scheduling intent when you automate workflows for social accounts. it focuses on what automation engineers need to know about payloads, permissions, approval, and publish behavior.
TTP uses an agent-driven MCP surface rather than exposing API keys. the agents accept structured inputs and route drafts into one approval queue. that architecture changes how you design error handling, auditing, and timing compared with a direct REST api.
agent-driven flow
submit a structured payload to TTP's agent surface with your content, target account, and optional suggested timestamp. agents validate and attach audit metadata, then place the draft in the platform approval queue.
a human reviewer must approve items in that single queue. after approval, TTP publishes to supported platforms. TTP chooses each account's best posting time by default unless you have an enabled workflow that honors strict timestamps.
practical integration items
prepare these items before you connect your automation to TTP's agents. they reduce back-and-forth with reviewers and prevent common validation failures.
include structured media references, locale and timezone metadata, source and change-id for audits, and the account id with permission scope. test the full submission-to-approval path in a staging account first.
permissions and plan limits
automation access runs through TTP's MCP surface and requires account permission. agents do not use API keys, so access is governed by TTP account roles and the agent interface. ensure your submitting identity has posting permission for the target account.
TTP offers a single, low-complexity plan for customers. programmatic automation and agent capabilities are available on that plan, subject to account-level limits and approval workflows. for high-volume or custom SLA needs, discuss options with the TTP team.
api choices
agent-driven scheduling centralizes approval, audit, and best-time publishing. it reduces the need to manage long-lived keys and shifts final publish control to human reviewers. this model benefits teams that require consistent governance and centralized review.
direct key-based apis from social platforms or other schedulers can offer lower-latency control and strict timestamp adherence. if your workflow requires raw endpoint calls and strict timestamp enforcement without a centralized approval step, those alternatives may be a better fit.
Questions for this workflow
TimeToPost does not use key-based public api endpoints for scheduling. instead, scheduling automation runs through the MCP surface where agents accept structured inputs and route drafts into the single approval queue. agents remove the need for api keys and centralize governance.
yes. submit structured payloads with your content, media references, and an optional suggested timestamp through TTP's agent surface. agents validate and enqueue the draft. note that after approval, TTP publishes using account best time logic unless your workflow is explicitly configured to enforce strict timestamps.
every draft lands in one approval queue and requires a human reviewer to approve it. automation must provide the account id and proof of permission so agents can route drafts correctly. access is governed by account roles rather than api keys.
after a human approves a draft, TTP can publish to Instagram, TikTok, and X. publishing behavior follows account best time logic unless a custom workflow has been enabled to respect exact timestamps.
Start with the workflow above, keep the human review gate, and adapt the cadence to the accounts you actually operate.
Start a review-first workflow