Social platforms

Batch-fetch TikTok videos by ID · TikTok API

POST/tiktok/videos/batch

Returns canonicalized metadata for up to 50 videos in a single call. Request body is a JSON array of numeric TikTok video IDs.

Request
curl https://api.unifapi.com/tiktok/videos/batch \
  -H "Authorization: Bearer $UNIFAPI_KEY"
Overview

This operation is part of the TikTok API in the social platforms category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.

Use it when a workflow needs TikTok public data but should still keep one API key, one account balance, and one predictable JSON contract across social, live public-data sources.

Common agent workflows

  • Fetch canonical public TikTok content for summarization, ranking, monitoring, or enrichment.
  • Attach engagement, author, media, and source metadata to an agent workflow.
  • Give an AI agent a stable TikTok data source without building a per-platform integration.
  • Normalize TikTok responses into the same UnifAPI envelope used across the catalog.
Response shape

Unified envelope, platform-native fields

  • Lookup responses return one canonical object in `data` with stable identifiers, source URLs where available, and platform-specific metadata normalized into predictable JSON.
  • Successful responses include `request_id` for support/debugging and `billing` with credits charged, records charged, and remaining balance.
  • A not-found or invalid-input condition uses the unified UnifAPI error shape, so callers do not need special handling for each upstream platform.

Billing

Every successful call costs at least one credit. List and search operations charge by billable records returned; single-object lookups charge one record when they succeed. Platform-caused failures can be refunded, and public responses include billing metadata with the credits charged and remaining workspace balance.

Errors and retries

Authentication, validation, rate-limit, not-found, and upstream errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.