Technical description · last updated 5 September 2026
FOLX Publisher runs on servers operated by PRIME TIME Consulting GmbH. It has no public interface: the whole cycle below runs unattended, on a schedule defined by our programming team. The only manual step in the entire system is the initial authorisation, which is performed once by the owner of the account being published to.
Before anything can be published, the tool needs permission to act on our TikTok account. A member of our team opens the authorisation link, is taken to TikTok's own login and consent screen, signs in as the account owner and approves the requested permissions.
TikTok then redirects back to our callback address with a temporary code, which our server exchanges for an access token and a refresh token. Those tokens are written to an encrypted credentials file on the server. The refresh token is used to renew access automatically so that the authorisation does not have to be repeated.
user.info.basic | Reads the open ID and display name of the connected account, so the tool can confirm it is publishing to the correct profile and can label its own log entries. |
|---|---|
video.publish | Uploads a video file and publishes it directly to the connected account, together with the caption prepared by the tool. This is the permission the scheduled publishing depends on. |
No other permissions are requested. The tool does not read comments, messages, followers, analytics or any content belonging to other TikTok users.
Our media library holds short-form versions of the music videos that air on the channels. At each scheduled slot the tool selects the next clip according to rules our editorial team defined: material that has not run recently, no repetition of the same artist within a day, and a match with the mood of the time of day.
The caption is built from the clip's own metadata — artist, track title, genre — and follows a fixed set of editorial rules of the broadcaster. Every caption is checked against those rules before the upload begins; anything that fails the check is discarded and the slot moves to the next candidate.
The tool initialises a Direct Post request, transfers the video file to TikTok in chunks, then polls the status endpoint until TikTok reports that processing is complete. When the post is live, the returned publish ID is written to our internal publishing log so the same clip is not queued again.
The video files are vertical, 1080 × 1920, produced from our own broadcast masters.
Every attempt — successful or failed — is recorded in our internal log with a timestamp, the clip identifier, the destination account and the result. If a scheduled post fails, our operations team is notified so the slot can be repeated. The log holds no information about other TikTok users.
| Access and refresh token | For our own account only. Stored on our server with restricted file permissions, replaced on every renewal, deleted when the authorisation is withdrawn. |
|---|---|
| Open ID and display name | Of our own account, used to confirm the publishing target. |
| Publishing log | Timestamp, clip identifier, caption, destination and result of each publishing attempt. |
| Nothing else | No personal data of viewers, no comments, no messages, no follower or audience data is requested, received or stored. |
FOLX Publisher