for software developers

social media api to create, inspect, and manage org-scoped posts

authenticated REST endpoints let your systems create drafts, inspect status, and trigger publish after human approval. integrates with TimeToPost drafts, scheduling, and monitoring for Instagram, TikTok, and X.

  • Human decision before publishing
  • Evidence and exceptions stay attached
  • No generated testimonial or outcome claim

feature

what the social media api does

the social media api provides authenticated REST endpoints to create, inspect, and manage posts at the organization scope. use the api to push drafts into TimeToPost, check draft status, update content metadata, and trigger publish actions once a draft is approved.

published content follows TimeToPost delivery paths to Instagram, TikTok, and X. drafts generated by TimeToPost features, including ideas, git commits, trends, or seo topics, can also be created or referenced through the api so your systems stay in sync.

  • create and update org-scoped drafts
  • inspect draft and publish status
  • trigger publish after human approval
  • works with posts drafted from ideas, commits, trends, and seo topics

security and limits

authentication, permissions, and plan limits

api access requires org-level authentication and role-based permissions. only accounts with the designated org role may create or manage organization posts through the endpoints.

access to the social media api is provided on TimeToPost s single plan. the platform enforces an approval queue. drafts created by the api remain pending until a human approver in your organization approves them. platform and third-party rate limits also apply and may affect publish timing.

  • org-level token and role required
  • single approval queue enforces human approval before publish
  • api access included on the single plan
  • third-party platform rate limits and publishing policies apply

developer workflow

how to build with the social media api

authenticate with an org token and confirm the calling identity has post management rights. create a draft object with content, media references, and metadata. the api will store the draft and mark it pending in the shared approval queue.

use inspection endpoints to poll draft state. once an approver publishes the draft, TimeToPost schedules delivery at the account best time and pushes to the selected platform. your integration should handle status transitions and platform error responses for reliable retries.

  • authenticate and verify org role
  • create draft with content and metadata
  • poll or subscribe to draft status for approval changes
  • handle publish outcomes and platform errors

integration points

connectors, content sources, and publishing targets

the api integrates with TimeToPost content sources. drafts can originate from ideas, git commits, trend signals, or seo topics. TimeToPost s AutoSEO blog engine and MCP surface coexist with the api; note that MCP agents run without api keys and are a separate automation surface.

for live posting, TimeToPost delivers to Instagram, TikTok, and X. choose between publishing via api-triggered workflows or using agent-driven MCP flows depending on whether you need programmatic control or agent automation.

  • support for drafts from ideas, commits, trends, seo topics
  • AutoSEO blog engine and MCP agents operate separately
  • live posting targets: Instagram, TikTok, X
  • pick programmatic api flows or agent-driven automation

evaluation guide

evaluate the social media api for your integration

confirm the api supports your must-have actions: create, read, update, delete drafts; inspect approval state; and trigger publish. verify org-level authentication and the required roles exist in your organization before development begins.

review the single approval queue behavior and plan inclusion. test error handling for platform rejections and account-level limits. if you rely on agent automation instead of programmatic control, consider the MCP surface where agents operate without api keys.

  • check supported actions and status fields
  • verify org roles and token provisioning
  • validate approval queue workflow with your approvers
  • plan for platform limits and agent-based alternatives

Questions for this workflow

Frequently asked questions

does TimeToPost provide a social media api for org-scoped posts?

yes. TimeToPost exposes authenticated REST endpoints to create, inspect, and manage posts at the organization scope. use the api to insert drafts, read status, and initiate publish actions once a human approver releases the draft.

how does the approval queue affect api-created drafts?

all drafts enter a single approval queue regardless of origin. api-created drafts remain pending and will not publish until a human approver accepts them. the queue enforces manual approval to prevent accidental publishing.

which platforms can the api publish to?

published posts are delivered to Instagram, TikTok, and X. confirm account-level permissions and platform-specific constraints before sending media or scheduling complex posts.

are there plan requirements or rate limits for api access?

api access is included on TimeToPost s single plan. the platform enforces role-based permissions and an approval queue. third-party platform rate limits and publishing policies also apply and may influence throughput and retry behavior.

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