TikTok post API

TikTok post data in one REST call — normalized to the stable JSON schema shared across every FetchPI platform.

1 documented endpoints
GET /v1/tiktok/posts/{id}

Contract summary (English): Get a normalized TikTok post (capability tiktok.post)

Normalized response entity: tiktok/post
capability: tiktok.post

Every response also carries freshness (cache / default / live) and billing metadata.

Use cases

Feed content-analysis pipelines with structured {{platform}} posts: text, metrics, timestamps and media references.
Power moderation, research and monitoring workflows that need the original content plus engagement counts.
Archive {{platform}} content as stable, normalized JSON instead of brittle page scraping.

Response fields

TikTok Post (normalized)

Normalized TikTok video post. Provider-private fields MUST NOT appear. Metric names are frozen (likes/comments/shares/collects/views); provider synonyms (digg_count/play_count/...) are mapped by the Normalizer. Missing upstream values normalize to 0.

Field	Type	Required	Description
id	string	Required	Numeric video id (aweme_id).
platform	"tiktok"	Required	—
type	"post"	Required	—
author.id	string	Required	Numeric uid.
author.username	string	Required	uniqueId.
author.display_name	string \| null	Optional	—
author.verified	boolean	Optional	—
text	string \| null	Optional	The video description.
created_at	string	Required	Post creation time, UTC RFC3339.
metrics.likes	integer	Required	Digg count.
metrics.comments	integer	Required	—
metrics.shares	integer	Required	—
metrics.collects	integer	Required	Favorites/saves.
metrics.views	integer	Required	Play count; 0 when not exposed.
attachments	object[]	Optional	Photo-post images and/or the video (cover preview + duration).
fetched_at	string	Required	—

Field notes are shown in the contract's original English.

Response meta

Field	Type	Required	Description
mode	cache \| default \| live	Required	Effective mode after merging param > max_age > source policy (D-004).
age_seconds	integer \| null	Optional	Age of served data; null when unknown.
source_layer	cache \| db \| upstream	Required	Which layer served the response (PRD §10).
stale	boolean	Optional	True when stale data was served under stale_if_error / SWR (D-004).
billing.amount_credits	integer	Required	Micro-USD (1e-6 USD) actually charged for this request.
billing.cache_hit	boolean	Required	—

Field notes are shown in the contract's original English.

Example request & response

GET/v1/tiktok/posts/{id}

curl -H "Authorization: Bearer $MESHDATA_API_KEY" \
  "https://api.fetchpi.com/v1/tiktok/posts/1842951234567890123"

{
  "data": {
    "id": "7410886000000000001",
    "platform": "tiktok",
    "type": "post",
    "author": {
      "id": "7004994945112",
      "username": "creatordev",
      "display_name": "Creator Dev",
      "verified": true
    },
    "text": "One API for every platform.",
    "created_at": "2026-09-17T12:34:56Z",
    "metrics": {
      "likes": 864,
      "comments": 42,
      "shares": 87,
      "collects": 310,
      "views": 154203
    },
    "attachments": [
      {
        "type": "video",
        "preview_image_url": "https://cdn.example.com/cover.jpeg",
        "duration_ms": 34567
      }
    ],
    "fetched_at": "2026-09-18T07:30:00Z"
  },
  "meta": {
    "request_id": "req_01HTXQ8Z9HTQ",
    "freshness": {
      "mode": "default",
      "age_seconds": 3600,
      "source_layer": "cache",
      "stale": false
    },
    "billing": {
      "amount_credits": 0,
      "cache_hit": true
    }
  }
}

Free demo

Create a free account, grab an API key and call this endpoint from the browser-based Playground.

Try it in the Playground

Parameter tables, error codes and response semantics for this endpoint live in the API documentation.

Open the endpoint reference

Frequently asked questions

Which content fields are included?

The normalized content entity — text, author, timestamps, engagement metrics and media references — as documented in the field table below, plus freshness and billing metadata.

Can I try this endpoint for free?

Yes — register an account, grab an API key and call it from the Playground in the console.

How is the post capability billed?

Data API calls are billed per request in credits, with different cache/live freshness multipliers. Current per-capability prices live on the pricing page.

Pricing

Per-request credit billing with cache/live freshness options — current prices live on the pricing page.

View pricing Browse all APIs