Does TimeToPost provide a traditional API key for approval actions?
No. TimeToPost surfaces programmatic approval through its MCP interface, driven by agents. The platform does not use external API keys for agent-driven approval actions.
feature: programmatic draft approval
social media approval api for workflow developers
List pending drafts and perform only the approval action allowed by the credential, using TimeToPost's agent-driven MCP surface with a single approval queue.
- Human decision before publishing
- Evidence and exceptions stay attached
- No generated testimonial or outcome claim
what this does
what TimeToPost provides for a social media approval api
TimeToPost exposes a programmatic approval surface through its MCP interface, driven by agents and not by external API keys. Drafts created from user voice, ideas, git commits, trends, and SEO topics wait in a single approval queue until a human approves them.
Workflow developers can list pending drafts and invoke the approval action that releases a draft to publishing. After approval the platform publishes to Instagram, TikTok, and X at each account's best time. Permission checks are enforced by the platform and the MCP surface, so the credential determines which accounts and actions are permitted.
- single approval queue for all drafts
- agent-driven MCP surface. no API keys
- publishes to Instagram, TikTok, X after approval
- drafts sourced from ideas, commits, trends, SEO topics
developer flow
how to list pending work and apply permitted approvals
Start by using the MCP surface agents to list drafts in the single approval queue. Filter results by the credential you are using so your workflow only sees drafts tied to accounts the credential may operate on.
When you run an approval action through the MCP surface, the platform enforces permission checks. If the credential permits publishing the draft is moved out of the queue and scheduled to publish at the account best time. If the credential lacks permission the platform will not apply the publish action.
- list queue items via MCP agents
- filter by account and credential scope
- attempt approval action via MCP surface
- confirm queue state and publish scheduling
permissions and plan limits
what the credential, approval, and plan controls mean for your workflow
Credentials determine which approval actions are accepted. The platform enforces those permissions at the time your agent or session attempts the approval transition. If a credential is not allowed to publish to an account the platform will reject that approval attempt.
TimeToPost is offered with a single low plan. The platform enforces permission checks, the single approval queue behavior, and live posting to Instagram, TikTok, and X. If you need broader integration patterns, plan inquiries and account connection limits are handled through the platform settings and support channels.
- credential scope controls which accounts a workflow can approve
- platform enforces permission checks on approval attempts
- single approval queue model applies to all drafts
- simple low single plan is the platform's current plan structure
integration tips
patterns for safe approval automation
Design your workflow to always verify credential scope before attempting an approval. Query the MCP surface for account bindings and only surface drafts that match the credential's permitted accounts.
Log each approval attempt and reconcile the post state after approval. Use the MCP agent responses to confirm whether a draft left the approval queue and whether it has a publish schedule or final post status for Instagram, TikTok, or X.
- pre-check credential account bindings before listing drafts
- filter pending work to the credential's permitted scope
- apply approval through MCP agents and check the response
- verify post schedule or publish status after approval
Questions for this workflow
Frequently asked questions
Which approval actions can my workflow perform?
Your workflow can list drafts in the single approval queue and invoke the approval transition that releases a draft to publishing. Whether the transition succeeds depends on the credential's permissions for the target account.
Which social networks does the approval flow publish to?
Once a draft is approved it is scheduled to publish to Instagram, TikTok, and X at each account's best time, as handled by the platform.
Are there plan or account limits I should design for?
TimeToPost is currently offered with a simple low single plan. Permission checks, the single approval queue, and publishing behavior are enforced by the platform. For account connection limits or enterprise needs, contact TimeToPost support to discuss options.
Turn this plan into an approval-ready queue
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