TikTok API 400: "Bad Request" (Encoding & Validation)

The Diagnosis: Why TikTok is Rejecting Your Request

Unlike the Facebook or LinkedIn APIs, which often attempt to transcode your media to fit their requirements, the TikTok Content Posting API is a "strict validator." If your video file doesn't perfectly match their expected schema, the API will not try to fix it for you—it simply returns a 400 Bad Request.

This error is almost never about your JSON syntax. Instead, it is a media validation failure triggered by one of the following "invisible" constraints:

• Bitrate Ceiling: TikTok's API generally caps video bitrates at 10 Mbps. If you are uploading high-quality 4K footage directly from a mobile device or professional camera (which can reach 30–50 Mbps), the API will return a 400 error.
• The Aspect Ratio "Purist": TikTok is a 9:16 platform. While the consumer app allows some flexibility, the API often rejects files that deviate by even a few pixels from the standard 1080x1920 resolution.
• The "Minimum Duration" Rule: TikTok requires videos to be at least 3 seconds long. If you attempt to post a 2.5-second clip, the API returns a 400.
• Incompatible Audio Codecs: TikTok requires AAC audio. If your video uses PCM or specialized Dolby codecs, the validation will fail.

The Manual Fix: Server-Side Sanitization with FFmpeg

To stop the 400 errors, you must "sanitize" every video before it hits the TikTok endpoint. You cannot simply pass a raw URL; you must ensure the file's DNA is TikTok-compliant.

Technical Implementation (FFmpeg Command)

Most developers solve this by running a pre-processing worker using FFmpeg. Here is the specific recipe to convert any video into a TikTok-ready format:

ffmpeg -i input_video.mp4 \  -vcodec libx264 \  -pix_fmt yuv420p \  -profile:v main \  -level:v 3.1 \  -maxrate 10M \  -bufsize 10M \  -crf 23 \  -vf "scale=1080:1920:force_original_aspect_ratio=increase,crop=1080:1920" \  -r 30 \  -acodec aac \  -ar 44100 \  output_tiktok_fixed.mp4

Why this is an engineering burden:

• CPU Overhead: Transcoding video is resource-intensive. Running FFmpeg workers at scale requires significant cloud compute (AWS EC2/Lambda) costs.
• Logic Complexity: You have to write "letterboxing" or "cropping" logic to handle landscape (16:9) videos without stretching them.
• Storage Management: You must store the "fixed" version temporarily, manage the upload, and then clean up the storage to avoid ballooning costs.

For more detail, see TikTok media guidelines.

The Ayrshare Solution: "Auto-Resize" Infrastructure

Ayrshare removes the need for you to manage an FFmpeg stack. We treat media validation as an infrastructure problem, not a code problem.

• Cloud Transcoding: When you send a video URL to Ayrshare, we automatically detect if it exceeds TikTok's bitrate or resolution limits.
• Smart Cropping & Padding: Using our autoResize: true parameter, we intelligently add black bars (letterboxing) to landscape videos or crop them to 9:16, ensuring they never trigger a 400 error.
• Managed Chunked Uploads: TikTok requires "chunked" uploads for larger files. We handle the split-and-stitch logic, which is a common source of 400 errors in manual implementations.

Comparison: Native vs. Ayrshare

const ayrshare = require("ayrshare-node")("YOUR_API_KEY");
const post = await ayrshare.post({  post: "Posting a 4K landscape video to TikTok.",  mediaUrls: ["https://your-site.com/raw-high-res-video.mp4"],  platforms: ["tiktok"],  autoResize: true // Replaces your entire FFmpeg infrastructure});

For more detail, see TikTok API documentation.

For more detail, see Handling TikTok Rate Limits (429 errors).

For more detail, see TikTok Account Restricted? How to Fix It.