developer resource for data engineers
how to get aggregate and per-post metrics from TimeToPost for downstream reporting, and which programmatic paths to choose
what this page covers
This page helps you evaluate transactional capability to retrieve aggregate and per-post metrics for downstream reporting. It describes current TimeToPost data surfaces, recommended architectures for programmatic access, and the permission and plan considerations to budget into an integration.
TimeToPost does not expose a public social media analytics api endpoint as part of the standard product documentation. Use the options below to decide whether dashboard exports, native platform APIs, or a custom agreement with TimeToPost best fits your reporting needs.
data surfaces and integrations
TimeToPost stores publishing activity, approval workflow state, and post identifiers for Instagram, TikTok, and X. Drafts wait in a single approval queue until a human approves, then the platform publishes at each account best time.
For SEO and related metrics, TimeToPost includes the Get Found suite. That suite contains keyword research, a rank tracker powered by DataForSEO, backlinks and outreach, AI mentions with GEO context, backlink exchange, and link analytics. These are available through the TimeToPost dashboard and agent driven MCP surface. The MCP surface is agent driven and does not require API keys.
options for programmatic retrieval
If you need reliable per-post metrics for reporting or BI, the most direct path is to call each social platform API. Native APIs are the authoritative source for impressions, reach, video views, and other per-post telemetry, and they require account level permission and platform OAuth.
If you prefer consolidated exports, use the TimeToPost dashboard and MCP agent outputs to pull post identifiers and available metrics, then join those to native platform data. For SEO metrics, use the DataForSEO rank tracker within TimeToPost. If neither approach meets your latency or format needs, contact TimeToPost to discuss programmatic access and a custom integration.
permission, approval, and plan considerations
TimeToPost requires account level permission to post and to surface related metrics. Each social account must grant consent to the corresponding platform. Drafts in TimeToPost remain in a single approval queue until a human approves, so automated publishing flows must account for that approval step.
TimeToPost offers a simple, low single plan for customers. Programmatic or custom access to consolidated analytics feeds is not part of the advertised public product. If you require an API or higher throughput exports, you must request a custom integration or enterprise arrangement. Any such arrangement is subject to contractual permission, agreed rate limits, and plan limits set at implementation.
choosing the right integration
Native platform APIs. Benefit, authoritative per-post metrics and near real time data. Trade off, you must manage OAuth for each account and reconcile identifiers between platforms and TimeToPost.
TimeToPost dashboard and MCP outputs. Benefit, consolidated view inside one product and easier joins for publishing metadata. Trade off, there is no public TimeToPost analytics api for automated high frequency pulls; exports may be manual or available via a custom agreement.
Questions for this workflow
No. TimeToPost does not offer a documented public social media analytics api as part of the standard product. Metrics are available in the dashboard and via the MCP agent surface, which is agent driven and does not use API keys. For programmatic access beyond dashboard exports, contact TimeToPost to discuss a custom integration or enterprise arrangement.
TimeToPost records publishing activity and post identifiers for Instagram, TikTok, and X. For authoritative per-post impressions, reach, and video views, use the native platform APIs with account consent. You can use TimeToPost exports to get post metadata and then join that to platform telemetry.
Every draft in TimeToPost waits in one approval queue until a human approves it, then the platform publishes at each account best time. Automated reporting flows must account for that approval step and for account level permissions granted to the social platforms. If you plan to publish and then immediately query metrics, factor in the approval timing and the platform reporting delay.
Contact TimeToPost support to request programmatic access, higher export frequency, or a custom feed. Such requests require explicit agreement, and any programmatic access beyond the standard dashboard is subject to permission, plan limits, and negotiated rate limits.
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