How-To Guide

How do you automate TikTok slideshows?

Automate TikTok slideshows through the two routes its photo-post API allows, direct post or an in-app draft, with the image, rate and pending-share caps.

9 min read

By the Superdirector editorial team. TikTok's Content Posting API documentation and the competitor and vendor guides named in this article were read November 14, 2026.

At a glance

How do you automate TikTok slideshows?

You automate a TikTok slideshow through the photo-post route in TikTok's [Content Posting API](https://developers.tiktok.com/docs/en/content-posting-api-reference-photo-post): serve the slide images as public URLs from a verified domain, then send one request carrying media_type PHOTO and the image list in the order the post should read. TikTok gives that request two routes. DIRECT_POST publishes the slideshow straight to the account, needing the video.publish scope. MEDIA_UPLOAD sends it to the creator's TikTok inbox as a draft to finish in the app, needing video.upload. Around the request an automation still has three separate jobs: produce the slides and caption, make the publish call, and keep the account posting on a schedule. TikTok documents the rules that job must respect, including six requests per minute per token, at most 5 pending shares in any 24 hours, and a daily post cap per account. This page walks both routes, the request, the caps, and what the API cannot do for you.

  • Two supported routes: DIRECT_POST publishes straight to the account; MEDIA_UPLOAD lands the slideshow in the creator's TikTok inbox as a draft, each behind its own scope authorization.
  • One slideshow is one request: up to 35 image URLs, a cover index, a 90-rune title and a 4000-rune description.
  • Success is read from the error code, and the documented caps are six requests per minute per token, five pending shares per 24 hours and a daily post cap per account.
TikTok's photo-post request forks two ways: DIRECT_POST publishes straight to the account under the video.publish scope with an audited client, while MEDIA_UPLOAD leaves a draft in the creator's inbox under video.upload.

Two routes, two scopes, two different people who finish the post. Original diagram from TikTok's photo-post reference, read November 14, 2026.

Superdirector

Make it work for your brand

Find it. Remake it. Post it. Superdirector turns the viral formats in your niche into your brand's carousels, X posts and video scripts, and keeps the calendar full.

What automating TikTok slideshows means

When someone searches for automating TikTok slideshows, three different jobs hide inside the one question. The first is production: generating or assembling the slide images, the caption and the title so a new slideshow exists at all. The second is publishing: making the call that puts that post on the TikTok account, with the music and privacy settings applied. The third is cadence: keeping the account posting new slideshows on a repeating schedule without a person re-opening the app each time. Competitor guides tend to collapse the three jobs so that one tool appears to do all of them, and each guide collapses them to its own product. TikTok's own documentation keeps the split clean, and that split is worth holding onto, because it decides what you build, what you buy, and where a person still decides something.

What TikTok itself supports is the second job and half of the third. Its Content Posting API carries a photo-post route that publishes a completed set of images either directly or as a draft, and the same API family documents the status checks that let a scheduler confirm the post landed. What TikTok does not offer inside that route is the first job: no field in the documented request generates slides, writes an image list, or drafts the caption. Production sits wherever your assets and an image workflow live, and the API takes over from a finished, ordered image list. The jobs, and where each one lives:

  • Produce the slides: assemble the images, write the title and description, decide the slide order. Lives in your own workflow or in whatever asset tool holds the images. TikTok's request only consumes the result.
  • Publish the slideshow: the photo-post request to TikTok's endpoint, in one of two modes. Lives in TikTok's API, behind the scopes and rules TikTok documents.
  • Keep the cadence: run the loop on a schedule, watch the publish status, and stay inside TikTok's rate and quota rules. Lives outside the app, because the native scheduler does not carry slideshows.

The rest of this page follows that order: the two routes TikTok allows, the image and text limits, the request itself, the music question, the timing question, and the honest list of what the photo-post API cannot do.

The two posting routes TikTok's API allows

TikTok's product page for the Content Posting API describes the pair of options the platform offers to outside apps: creators can post content directly from your app to their TikTok profile, or upload it to TikTok as a draft for further editing. Both routes take a photo post, so both are available to a slideshow automation. The product page names the split in its own terms: the Direct Post API lets creators post content directly from the app to their TikTok profile, while the Upload API sends draft content that arrives in TikTok as an inbox notification telling the creator the content is ready for further editing.

The photo-post reference turns that split into two request-level settings. The post_mode field takes either DIRECT_POST, which directly posts the content to the TikTok user's account, or MEDIA_UPLOAD, which uploads the content for the user to complete in TikTok's editing flow after an inbox notification. Which mode an automation can actually use depends on authorization and audit status, not on preference:

RouteWhat happensWhat it requiresWhat the creator sees
DIRECT_POSTThe slideshow publishes straight to the accountThe TikTok user must have authorized the app for the video.publish scope; the app should be audited, because unaudited clients can only post to private accountsA live photo post, with privacy and comment settings applied from the request
MEDIA_UPLOADThe slideshow lands as a draft in TikTokThe TikTok user must have authorized the app for the video.upload scope, with the app approved for that scope firstAn inbox notification, then TikTok's own editing flow, where they finish and post it themselves

One asymmetry matters for a hands-off build. On the direct route, the request sets privacy_level from the options the creator_info query returns, and a value that does not match them is an error, private_mode aside. On the draft route, the creator completes those settings in app. That is why wrapper vendors advise draft mode when a specific post's reach matters most, and Upload-Post's platform page frames the trade-off in exactly those terms, DIRECT_POST for hands-off high-volume automation and MEDIA_UPLOAD when reach on a specific post matters most. That is vendor guidance about reach rather than a measured result, but the underlying mechanics are documented in TikTok's reference: the draft route hands the finishing choices to the creator in TikTok's own flow.

Prepare the slideshow images within TikTok's limits

The photo-post route consumes an ordered list of image URLs, so preparation is mostly about the shape those URLs take. TikTok's reference fixes the fields: photo_images is an array containing up to 35 photo content URLs, publicly accessible and verified by your app, and photo_cover_index picks, counting from 0, which photo shows as the cover. The transfer method is fixed too: for photo posts only PULL_FROM_URL is allowed, and using it requires the developer to verify ownership of the URL prefix or domain that serves the images. TikTok's get-started guide states the same need from the reading side: you need to provide a URL of a photo from your verified domain or URL prefix. In practice that means the images a slideshow automation ships live on an address TikTok has verified, not on an arbitrary file host.

The text fields have their own bounds, and both matter for a slideshow because the title rides on the first slide and the caption carries the post. The title's maximum length for photo posts is 90 in UTF-16 runes, and the same cap applies to the description at 4000 runes. An automation that writes its own titles needs those limits checked at write time, not at publish time, since a 400-rune title is a rejected request rather than a trimmed one.

Sizing comes from how TikTok renders sliders, with PostEverywhere's spec guide documenting Photo Mode as supporting 4 to 35 images at 1080x1920 pixels for 9:16 vertical display, exactly the range the official array cap reaches. Keep the images at the aspect ratio the account actually posts in, ordered as the arrays go, cover first unless you mean otherwise: the array order is the post's slide order.

Choose the posting mode before you build the request

Post_mode is a single request field, but the choice behind it is an operating decision, because each route needs its own scope and fails in its own way. The photo-post reference is explicit about the authorization: to use Direct Post, the target TikTok user must have authorized your app for the video.publish scope, and to use the upload method they must have authorized it for the video.upload scope. The get-started guide adds the app-side half: the app must be approved for the video.upload scope before the upload route works at all, and the call needs the access token and open ID of the TikTok user who authorized your app.

The audit rule is the one that surprises new builds. Until an API client has been audited, the reference states that all content posted by unaudited clients will be restricted to private viewing mode, and unaudited clients can only post to private accounts, with publish attempts otherwise blocked. A prototype that behaves perfectly against a test account can therefore look broken the day it points at a public account. Plan the route around the account reality: for a private test account either mode works; for a public account running hands-off, the direct route needs an audited client behind it, and the draft route needs a creator willing to finish posts in the inbox.

Vendors give the practical reading. Upload-Post's TikTok platform page advises DIRECT_POST for hands-off, high-volume automation and draft mode when reach on a specific post matters most, their own advice, stated as such. Blaze's account-automation guide shows what the draft route looks like in a product flow: its walkthrough makes publishing follow a review step first, then publishes automatically on schedule. Both readings settle onto the same decision rule, which the official error codes make concrete: choose the route by asking, for each post, whether the account can and should publish it unattended, and let the mode follow that answer.

Send the photo post request

The request is one POST to TikTok's content init endpoint, with a Bearer user access token in the Authorization header and a JSON body carrying three objects. The get-started guide is blunt about the endpoint choice: use /v2/post/publish/content/init/ to upload photos instead of the video init route, because photos are a different case in the same API. The body: post_info carries the title, description, privacy settings and the auto_add_music flags; post_mode carries DIRECT_POST or MEDIA_UPLOAD; media_type is PHOTO, the only value the reference allows for photo posts; source_info carries PULL_FROM_URL, the photo_images array and photo_cover_index.

One content-disclosure field deserves a line of its own: is_aigc, set to true when the photo is AI-generated content, makes the post carry an AI-generated label in the description. For automated slideshows built from generated imagery, that flag is part of publishing honestly. Whether your slideshow needs it or not, the field names the line TikTok draws in its own reference, and the wrapper APIs expose it too, field for field.

The response is the part an automation actually reads. A 200 returns data.publish_id, an identifier that tracks the posting action through the status-fetch endpoint, and error.code. TikTok's rule for reading it: any code other than ok indicates the request did not succeed. That ordering matters operationally: the publish_id is only useful when the code is ok, and a build that treats HTTP 200 as success will silently accept failures. The documented failure codes, the daily post cap (spam_risk_too_many_posts), the pending-share ceiling (there may be at most 5 pending shares within any 24-hour period), the privacy mismatch, the unverified domain and a 429 rate_limit_exceeded, are all configuration and quota signals rather than network flukes, so a retry loop that ignores them just burns against the same wall faster.

An annotated map of TikTok's content-init request: a Bearer authorization header, then post_info, post_mode, media_type of PHOTO and source_info in the body, answered by publish_id and error.code.

The body is three objects behind one header, and the response is what an automation reads. Original diagram from TikTok's photo-post reference, read November 14, 2026.

Attach music or finish the draft in TikTok

Music is the difference between a slideshow that reads and one that plays like a muted film. The official field for the direct route is auto_add_music, and the reference is precise about what it does and where: it only works with post_mode equal to DIRECT_POST, and when set to true, recommended music will be automatically added to photos, with users later able to change the post's music in TikTok if they prefer something else. That setting is TikTok's recommendation engine, not a trending-sound picker, and no documented field lets the request name a track.

Practitioner experience matches the mechanics. UGC API's slideshow guide states the observation directly: TikTok photo posts without sound perform like a muted video, and its auto_music option maps to TikTok adding a recommended track the creator can change in the app. The conclusion both vendors and the documented fields converge on: silence is the default failure, the music flag is the default fix, and anything more specific than a recommendation needs a human in the loop.

When the job needs that specific sound, for example posting into a trend where one audio is the point, the supported path is the draft route twice over: MEDIA_UPLOAD sends the slideshow to the creator's TikTok inbox, the creator finishes the post in TikTok's editing flow with the audio they choose, and the automation's job ends at the inbox notification. That is the same trade-off the mode section set out, now with a concrete trigger: automate the default, route the exceptions to the draft inbox, and do not let the automation guess which songs are trending.

Schedule the repeat run and respect the caps

The native scheduler is out. PostEverywhere's guide states it plainly: TikTok's native scheduler does not support carousel or Photo Mode posts, it only works with video content. So the cadence job lives outside the app, in whichever layer runs the loop: your own scheduler on the API route, a wrapper endpoint with scheduling built in, or an operated account where the service runs the schedule. Upload-Post's TikTok page documents the wrapper shape, a scheduled_date field taking a future date and time up to 365 days ahead, and their pricing page places TikTok uploads on its paid plans only, stating plans start at $24 a month as of its November 14, 2026 reading, a declared vendor price worth checking against your own invoice before you build on it.

Whatever runs the schedule, TikTok's documented caps bound it. The photo-post reference sets the request rate: each user access token is limited to six requests per minute, and a 429 code, rate_limit_exceeded, answers a run that shoves past it. The account has stricter ceilings still: spam_risk_too_many_posts fires when the daily post cap from the API is reached for the user, and pending uploads of the draft kind have their own rule, that there may be at most 5 pending shares within any 24-hour period, which is TikTok's stated anti-spam design limiting how many API uploads can sit awaiting the creator's action at once.

Two operating rules keep a scheduled slideshow loop inside the caps in practice, and both come straight from the documented behavior rather than from anyone's promise. First, serialize: one publish attempt per account per interval, checked against the previous request's error code, since a single account posting through one token cannot outrun the six-per-minute rule without retry logic that multiplies it against the cap. Second, treat drafts as pending inventory: each MEDIA_UPLOAD delivery sits against the five-pending ceiling until the creator acts on it, so a draft-heavy cadence needs the inbox drained, not just refilled. The daily cap itself is deliberately unnumbered in the public docs, so a schedule that would post near-daily slideshows should watch for spam_risk codes and back off, not assume room nobody has measured.

What TikTok's photo-post API cannot do

An honest automation plan starts from what the route does not carry. The documented request for a photo post has fixed fields: post_mode, media_type, the post_info fields, and the source_info trio. Nothing in that set carries per-slide timing, so how long each slide holds is not something the request controls; template-style auto-advancing presentations are a creation-flow feature rather than a request field, and PostEverywhere's guide describes Template Mode as playing like a video, timed to music, from inside the app. Nothing names a track: auto_add_music reaches only recommended music. Nothing schedules in native: the scheduler takes videos only. Those absences are stable, documented ones, which makes them plannable.

The quota walls are real too, and worth restating as limits rather than as obstacles. Six requests per minute per token, five pending draft shares per 24 hours, a daily post cap of unnumbered size, and an unaudited client boxed to private accounts: each one bounds what a hands-off slideshow loop can do on a single account per day, and none is negotiable from the request side. A loop that needs more volume than one account allows needs a second account and its own authorization, not tighter retry logic against the same token.

And there is a compliance floor worth writing down, because the search results for this question are full of tools blurring it. Blaze's automation guide puts it as a rule: never automate mass following, generic commenting, or engagement pods. The photo-post API is a publishing interface, exactly and only that; anything that reaches beyond publishing into growth tactics steps outside what TikTok's documented surface supports and into territory that risks the account itself. A slideshow automation that stays inside it publishes what a person would have posted, just on time, every time.

Four documented limits on automated photo posts: six requests a minute per token, five pending draft shares in any 24 hours, an unnumbered daily post cap signalled by spam_risk_too_many_posts, and private-only posting for unaudited clients.

Each cap is TikTok's, not the tool's, and none is negotiable from the request side. Original diagram from TikTok's photo-post reference, read November 14, 2026.

Operate it as a standing account job

The three-job split at the top of this page turns into three operating models, each with a different bill and a different place where a person decides something. Build it yourself against TikTok's API: free to attempt, but the audit gate is the price of public posting, and the scopes, verified domain and status handling are yours to maintain. Buy the publish layer: wrapper APIs carry TikTok posting on their own paid tiers, with Upload-Post naming $24 a month as its floor for TikTok, their declared price, and their endpoints taking the same fields for mode, music and scheduling this page has walked. Own the whole loop: an operated account runs production, the publish call and the cadence as one standing service.

Superdirector (ours) sits in the third model. The $29 a month plan is MCP access and hands-on creation from inside Claude or ChatGPT, which pairs with the API route where you or your agent wants to make the publish calls yourselves. The $199 a month plan is one AI-run operated social account: Superdirector produces posts in the owner's direction and publishes them under standing, account-level permission, which is a different shape from asking a person to approve every single post, and a different shape again from the draft-in-box flow TikTok's upload route offers creators. The caps and rules this page documents, the scopes, the pending-share ceiling, the daily quota, bind every model equally, because they are TikTok's, not the tool's.

Whichever model you pick, set the loop up to prove the job, and keep the person in the loop at the boundaries the rules leave human. Read the publish_id status after each request rather than assuming the 200 carried through; check the inbox load before piling on draft deliveries; watch for the spam_risk codes and treat them as the account asking for space rather than as failures to override. And where a specific trending sound or a judgment call about the feed matters, route that post to the draft inbox or to a person instead of teaching the automation to guess. That discipline is what separates a slideshow operation from a slideshow farm, and it fits inside every rule TikTok documents.

Frequently asked questions

Can you automate TikTok slideshows through TikTok's own API?

Yes. TikTok's Content Posting API now supports sending photos, and its photo-post reference documents a single endpoint, /v2/post/publish/content/init/, that posts photos either directly to the account (DIRECT_POST) or as a draft for the creator to finish (MEDIA_UPLOAD). The request carries the slide images as an array of up to 35 public URLs, a cover index and the usual post fields. What the API does not do is generate the slides for you: producing the images, the caption and the title stays your job, and only the publish call and the draft flow are TikTok's to run.

Do you need a TikTok developer app and an audit to automate slideshows?

For a build of your own, yes to the app. TikTok's get-started guide lists the prerequisites: a registered app with the Content Posting API product added, approval and authorization of the video.upload scope (or video.publish for direct posting), and the access token and open ID of the TikTok user who authorized your app. Photos must be served from a verified domain or URL prefix. One hard rule changes the decision for most small teams: all content posted by unaudited clients lands in private viewing mode, and an unaudited client's direct publish attempts are blocked. The audited-client review is why many teams reach for a wrapper or an operated account instead of building against the API directly.

How many images can one automated TikTok slideshow carry?

The photo-post request accepts an array of up to 35 photo content URLs, and the URLs must be publicly accessible and verified. PostEverywhere's spec guide puts the same range in app terms, Photo Mode supporting 4 to 35 images, and recommends 1080x1920 pixels for full-screen display. The array order is the slide order, and photo_cover_index, which counts from 0, picks which image shows as the cover.

Can automated TikTok slideshows get music added?

Two ways. On the direct-post route, auto_add_music set to true makes TikTok add recommended music to the photos automatically, and the creator can later change the post's music in TikTok if they prefer something else. UGC API's slideshow guide adds practical context for the choice: a TikTok photo post without sound performs like a muted video, so silent slideshows are the failure mode to avoid. If the job needs one specific trending sound rather than a recommendation, the draft route is the supported path: MEDIA_UPLOAD sends the slideshow to the creator's TikTok inbox, where they finish the post in the app with the audio they pick.

Why did my automated slideshow fail to publish?

Judge success by the response's error code, since any code other than ok means the request did not succeed. The photo-post reference documents the failure modes an automation actually hits: spam_risk_too_many_posts, the daily post cap being reached for the account; spam_risk_too_many_pending_share, no more than 5 pending shares allowed in any 24-hour period; privacy_level_option_mismatch, the privacy value not matching the options returned by the creator_info query; url_ownership_unverified, images served from a domain the developer has not verified; and rate_limit_exceeded at HTTP 429 when requests outrun the six-per-minute limit. Each of these is a rate, quota or configuration problem to fix at setup, not an outage to retry blindly.

Does TikTok's native scheduler support slideshows?

No. PostEverywhere's guide states TikTok's native scheduler only works with video content, so slideshows cannot be scheduled in advance from the app. Outside the app there are two supported paths: the API itself, and wrapper APIs whose endpoint takes a scheduled_date, with Upload-Post documenting a future publish date up to 365 days ahead. Upload-Post's pricing page also puts TikTok on its paid plans only, its page stating plans start at $24 a month, which is worth checking before you build on a wrapper's free tier. An operated account is the third path, where the publishing service keeps the schedule inside those same platform rules.

Related practical guides

Watch the first automated runs

After the first scheduled slideshow publishes, read the request's error code and the publish status, check the pending-draft count before the next delivery, and back the cadence off when a spam_risk code appears.