TikTok Analytics API
The TikTok Analytics API brings TikTok video performance data into a product, reporting workflow, automation, or AI system through one API.
curl "{{API_BASE_URL}}/v1/analytics?platform=tiktok&accountId=acc_tt_321&sortBy=views&order=desc&limit=10" \
-H "x-access-key: your-api-key"curl "{{API_BASE_URL}}/v1/analytics?platform=tiktok&accountId=acc_tt_321&sortBy=views&order=desc&limit=10" \
-H "x-access-key: your-api-key"
It retrieves TikTok video views alongside TikTok likes comments shares for supported videos, so a dashboard can show per-video performance without maintaining a separate analytics integration for TikTok. Connected Account Analytics uses a connected TikTok account to retrieve video performance through the same analytics workflow used across supported platforms, with filtering, sorting, and pagination for larger result sets.
What the TikTok Analytics API returns
The TikTok Analytics API returns per-video performance for supported TikTok videos, including TikTok video views and TikTok likes comments shares. That makes it suitable for a TikTok video performance dashboard, a SaaS reporting view, an internal analytics workflow, an automation, or an AI system that needs structured video metrics rather than manually collected screenshots or spreadsheets. Per-Video Metrics are the core unit: each returned post carries an aggregated metric object and a platform-specific metric object for TikTok, so the same normalized shape can be reused when other supported platforms are added later.
Connected account and OAuth workflow
Connected Account Analytics starts from a connected TikTok account. TikTok is connected through an OAuth flow, and the resulting integration identifier is used throughout the API workflow as the accountId value in requests. Once connected, the same unified analytics endpoint, /v1/analytics, is used instead of maintaining a separate analytics integration for TikTok. A practical integration sequence is to obtain an API key, connect the TikTok account once, and then call the analytics endpoint with the connected account identifier. Check that the account identifier matches the connected integration before debugging metrics, because a mismatched accountId will not return the intended account's videos.
Sorting, pagination, date range and single-video retrieval
Performance Sorting lets a product organize TikTok video results by supported analytics sorting parameters, including video-performance metrics such as views. The captured example sorts by views in descending order to surface top videos, and the source also describes sorting by likes, comments, and shares. For larger collections, split retrieval across pages by combining page with limit, so each response stays manageable. For a dashboard, request a small limit first to validate the account and response shape, then increase limit or advance page only when the full result set is needed. For a single video, include the TikTok video identifier alongside platform=tiktok and the connected account identifier. For existing videos not published through this API, set source=platform and supply the connected account identifier, so recent TikTok items can be fetched straight from TikTok even when they predate any use of this API. Date filtering is described as supporting a custom date range of up to 366 days for campaign reports or historical comparisons; confirm the exact date parameter names and formats against the full reference before implementing them, because they were not fully enumerated in the captured source.
Related capabilities and implementation checks
Beyond analytics, the same connected TikTok workflow can support related capabilities such as TikTok posting and TikTok scheduling, and the same API pattern extends to other supported platforms including Twitter/X, YouTube, Pinterest, LinkedIn, Facebook, and Instagram, as well as posting, scheduling, comments, messaging, and comment-to-DM capabilities. Those related capabilities are context for planning a broader social workflow; they do not change the analytics request or response contract described here. When evaluating the integration, verify the exact HTTP method, required parameters, authentication failure behavior, and error responses against the full API reference before treating the workflow as production-ready, because the captured source fully specifies only the example request and its 202 response.
| Parameter | Location | Captured example value | Requiredness / type / enum | Notes |
|---|---|---|---|---|
| platform | Query string | tiktok | Not fully enumerated in captured source | Selects TikTok analytics. |
| accountId | Query string | acc_tt_321 | Not fully enumerated in captured source | Connected TikTok account / integration identifier. |
| sortBy | Query string | views | Not fully enumerated in captured source | Performance Sorting field; source also describes likes, comments, shares. |
| order | Query string | desc | Not fully enumerated in captured source | Sort direction in captured example. |
| limit | Query string | 10 | Not fully enumerated in captured source | Pagination page size. |
| page | Query string | Not shown in captured example | Not fully enumerated in captured source | Pagination page number; described in source for larger result sets. |
| x-access-key | Header | your-api-key | Not fully enumerated in captured source | API key header in captured example. |
Requiredness, types, enums and defaults not fully enumerated in captured source; do not invent them.
| Field | Location | Type in captured example | Meaning |
|---|---|---|---|
| success | Top level | boolean (true) | Request success flag. |
| total | Top level | number (1) | Total matching results in the example. |
| page | Top level | number (1) | Current page. |
| limit | Top level | number (10) | Page size used for the request. |
| posts | Top level | array | Returned video/post objects. |
| posts[].source | Post object | string ("platform") | Origin of the post data; source=platform retrieves existing TikTok videos. |
| posts[].postId | Post object | null in example | Internal post identifier; null for platform-sourced example. |
| posts[].content | Post object | string | Video/post text content. |
| posts[].publishedAt | Post object | string (ISO 8601) | Publication timestamp. |
| posts[].aggregated | Post object | object | Normalized cross-platform metric object. |
| posts[].platforms[].platform | Platform entry | string ("tiktok") | Platform identifier. |
| posts[].platforms[].platformPostId | Platform entry | string | TikTok video identifier. |
| posts[].platforms[].platformPostUrl | Platform entry | string (URL) | Link to the TikTok video. |
| posts[].platforms[].metrics | Platform entry | object | TikTok-specific metric object with the same normalized fields. |
Types inferred only from the captured example values; full schema not supplied.
| Metric field | Supported for TikTok in captured example | Example value | Notes |
|---|---|---|---|
| views | Yes | 42100 | TikTok video views. |
| likes | Yes | 1842 | TikTok likes. |
| comments | Yes | 73 | TikTok comments. |
| shares | Yes | 218 | TikTok shares. |
| impressions | No (null) | null | Predictable null field in normalized schema. |
| reach | No (null) | null | Predictable null field in normalized schema. |
| saves | No (null) | null | Predictable null field in normalized schema. |
| clicks | No (null) | null | Predictable null field in normalized schema. |
| engagementRate | No (null) | null | Predictable null field in normalized schema. |
Supported vs null fields are as shown in the captured example; full metric availability may vary by video and account.
| Scenario | How to request it | What to check | Failure / limitation check |
|---|---|---|---|
| Top videos for a connected account | platform=tiktok with accountId, sortBy=views, order=desc, limit | posts[] sorted by views descending; aggregated and platforms[].metrics agree | Wrong accountId returns the wrong account's data or no results; verify the connected integration ID. |
| Existing videos not published through this API | source=platform with the connected TikTok account ID | Recent TikTok videos returned directly from TikTok | Do not assume only API-published posts are included; platform-sourced retrieval covers existing content. |
| One specific TikTok video | TikTok video ID together with platform=tiktok and the connected account ID | Single video's views, likes, comments, shares | Exact single-video parameter name not enumerated in captured source; confirm before implementing. |
| Larger result sets | page and limit | total, page, limit reflect the requested slice | Requesting everything at once can be inefficient; paginate instead. |
| Historical / campaign reporting | Custom date range up to 366 days per source FAQ | Results limited to the requested range | Exact date parameter names and formats not enumerated in captured source; ranges beyond 366 days are not described as supported. |
| Unsupported metric fields | Read the normalized metric object | impressions, reach, saves, clicks, engagementRate are null for TikTok in the example | Do not treat null fields as zero; they indicate the metric is not supported for TikTok in this schema. |
Date parameter names/formats and single-video parameter name not fully enumerated in captured source; confirm against full reference before implementing.
Frequently asked questions
Which TikTok metrics can I retrieve?
Supported TikTok video metrics include views, likes, comments, and shares. The normalized response keeps unsupported fields predictable, including impressions, reach, saves, clicks, and engagementRate, rather than requiring a different schema for TikTok.
Do I need to apply for the TikTok Display API myself?
The captured source states that the TikTok integration and approved video.list access are handled through the connected workflow, so a separate TikTok developer application and Display API audit are not described as required for this workflow. That approval claim is held for verification and is not presented here as independently confirmed.
Can I retrieve analytics for videos I did not publish through this API?
Yes, according to the captured source. Set source=platform and supply the connected account identifier, so recent TikTok items can be fetched straight from TikTok even when they predate any use of this API.
Can I get analytics for one specific TikTok video?
Yes. Include the TikTok video identifier alongside platform=tiktok and the connected account identifier, and the response should contain that item's supported performance figures.
Can I filter TikTok analytics by date?
Yes. The captured source describes analyzing TikTok videos over a custom date range of up to 366 days for campaign reports or historical performance comparisons. The exact date parameter names and formats were not fully enumerated in the captured source.
Can I sort TikTok videos by performance?
Yes. Ordering can follow any supported TikTok metric among views, likes, comments, and shares, which helps surface the strongest performers in a product view.
How much does a TikTok analytics request cost?
The captured source states that each analytics API call costs 1 credit, regardless of how many videos are returned. That credit statement is preserved as a source contract detail and is held for owned implementation verification rather than presented as a live commercial offer.
{
"success": true,
"total": 1,
"page": 1,
"limit": 10,
"posts": [
{
"source": "platform",
"postId": null,
"content": "A short example update.",
"publishedAt": "2026-05-28T14:22:00Z",
"aggregated": {
"impressions": null,
"reach": null,
"likes": 1842,
"comments": 73,
"shares": 218,
"saves": null,
"clicks": null,
"views": 42100,
"engagementRate": null
},
"platforms": [
{
"platform": "tiktok",
"platformPostId": "7123456789012345678",
"platformPostUrl": "https://www.tiktok.com/@youruser/video/7123456789012345678",
"metrics": {
"impressions": null,
"reach": null,
"likes": 1842,
"comments": 73,
"shares": 218,
"saves": null,
"clicks": null,
"views": 42100,
"engagementRate": null
}
}
]
}
]
}