Developer integration
How ParkourFlux uses the TikTok API
The ParkourFlux publishing tool is a first-party, single-operator application. It exists to upload videos that ParkourFlux produces to ParkourFlux's own TikTok account. It is not offered to third parties, has no other users, and does not read or collect anyone else's content.
Single-account scope. The application is authorised by one TikTok account — the account that owns this channel — and can act only on that account. There is no sign-up, no user directory, and no mechanism for another person to connect an account.
Permissions requested, and what each is for
| Scope | Why it is needed |
|---|---|
user.info.basic |
Confirms which account the token belongs to, so a video cannot be uploaded to the wrong destination. Used to display the authorised account when checking the integration; no profile data is stored. |
video.upload |
Uploads a finished video into the account's own drafts/inbox. The operator then opens TikTok and posts it manually. This is the current mode of operation. |
These two are the only permissions the application requests. It does not
ask for video.publish: nothing is posted to the account
directly, so the permission to do so is not needed.
The publishing flow
- A video is produced The pipeline renders a finished vertical video. Nothing has touched TikTok yet.
- The operator approves it The finished file is reviewed and explicitly approved. Rejected videos are never uploaded.
- It is uploaded to drafts The approved file is sent to the account's own TikTok drafts. It is not published. The operator opens TikTok and posts it themselves.
- The result is logged Success or failure is written to a local log. Failures stop the run rather than retrying.
Who chooses the privacy setting
The creator does. A video sent to drafts is not published by this application, so it carries no audience setting of its own — privacy, caption and everything else are chosen in the TikTok app at the moment the creator decides to post it.
What data is stored, and where
- An OAuth access and refresh token for the single authorised account, stored locally on the operator's own machine in a file that is excluded from version control. It is never transmitted anywhere except to TikTok.
- A local publishing log recording which of our own videos were uploaded and when.
No TikTok user data is collected, no analytics about other accounts are gathered, no content belonging to anyone else is read or downloaded, and nothing is shared with third parties. There is no server-side database — the tool runs on a single machine.
Revoking access
Access can be withdrawn at any time from the TikTok account's Security & permissions → Manage app permissions screen. Revocation takes effect immediately; the stored token stops working and the tool can no longer upload.
Contact
Questions about this integration can be sent to mindcraftkrish.patel@gmail.com. See also our privacy policy and terms.