TikTok oEmbed: embed a posted clip, or host the MP4 yourself?

To embed a TikTok on your own page, call GET https://www.tiktok.com/oembed?url=<video url> and paste the returned html into the page. If the clip was made with Sume and you only need people to watch it, hosting the MP4 yourself avoids a third-party script; if you want TikTok's own player on the page, use the embed.

The two options solve different problems, so the decision is about what the page is for.

What does the TikTok oEmbed endpoint return?

TikTok's embed documentation describes a single required parameter, url, the video link. The response follows the oEmbed specification: version, type (video), title, author name and URL, an html string, width and height, thumbnail URL with its dimensions, and provider name and URL. Width and height are both reported as "100%".

The html is a blockquote with the class tiktok-embed, carrying attributes such as data-video-id and data-embed-from="oembed", plus a script tag that loads TikTok's embed code. TikTok's page does not state rate limits or caching rules, so cache the response on your side and avoid calling it on every page view.

curl -G "https://www.tiktok.com/oembed" \
  --data-urlencode "url=https://www.tiktok.com/@scout2015/video/6718335390845095173"

When should you embed instead of hosting the file?

The embed is right when the page should show the post as it lives on TikTok, with TikTok's player and the creator details the response carries. It also keeps the video inside TikTok's own delivery, so you carry no bandwidth for it. The trade-offs are an external script on your page, a layout you do not control beyond the 100% width, and a dependency on the post staying public.

Hosting is right when the page is a product page or a landing page where the clip is part of your design. You choose the poster frame, autoplay behavior and caption style, and the video does not vanish if the TikTok post is removed.

How does a Sume clip fit either route?

Sume jobs return a result you fetch through jobs and results; an avatar clip is a finished video on media.sume.com. For hosting, point your video tag at that artifact URL, or copy it to your own storage if you want control over caching. For a poster image, use video frames with at: [1.5] to pull a still at a time you name.

For the embed route, you first post to TikTok yourself; Sume does not post. After the post is live, take its URL and run the oEmbed call above.

What are the caveats?

Use public posts only; an oEmbed call for a private video is not something TikTok's page describes, so test before you build. Check your own embed in a mobile browser, since 100% width inside a narrow column behaves differently from a full-width layout. Finally, if the clip is AI-generated, decide how you disclose it on your own page too; the embed shows whatever TikTok shows, and a hosted MP4 shows only what you add.

A last practical point on thumbnails: the oEmbed response includes a thumbnail URL with dimensions, which is handy for a lightweight link preview that loads the full embed only on click. That keeps the page fast while you still show the real post. For a hosted file, generate your own poster with Sume's frame extraction and set it on the video tag, so the first paint matches the clip's best moment instead of a blank frame.

Think about maintenance too. An embed is one line of markup that TikTok keeps current, so a design change on their side reaches your page without a deploy. A hosted file is yours to keep: you re-encode it if a browser drops a codec, and you pay for the traffic. For a short marketing clip, that cost is small; for a library of hundreds of clips, it adds up, and the embed route may be easier to run.

Whichever you choose, keep the Sume job id next to the page entry. If the clip needs a correction, you regenerate from the same script, repost or replace the file, and update the page once.