TikTok Creator Desk: Uploads, Reposts and Live Sessions

This is a reproducible reference deployment based on shipped 1322 behavior. It is not presented as a named-customer testimonial and makes no claim about trading returns. The operating figures below are typical ranges rather than an SLA.

• The TikTok product ships tiktok.upload.created, tiktok.repost.created, tiktok.live.started and tiktok.live.ended under the schema 1322.tiktok.event.v1, plus a sibling tiktok.media.ready frame under 1322.tiktok.media.v1 carrying the downloadable file.
• Live start and live end are separate events carrying the same room_id, which is what allows one alert to be opened and later closed.
• REST and WebSocket use two distinct credentials that are not interchangeable, and the working consumer is published as a Python tutorial.

• No official TikTok developer surface can watch a public creator: each one is scoped to a creator who has connected their own account to the app.
• A live session cannot be caught late; once it ends there is nothing left on the profile to find, so a delayed notification is the wrong notification.
• Tools that fire a single live ping leave stale alerts behind, and a repost flattened into an upload misattributes whose video is actually spreading.

• Create a tracked list of the public creators the desk cares about, by @username, over REST, from the dashboard or with the Discord bot.
• Use the included Discord bot when the audience is a channel, and add WebSocket delivery when the desk wants the raw event in its own code.
• Branch on the event type rather than the text: uploads, reposts, live starts, live ends and media-ready each mean something different.
• Key open live sessions by the room_id shared between the start and end events so one session produces one alert.

1. A tracked creator uploads, reposts another creator's video, or opens a live session.
2. 1322 converts the source event into the documented TikTok event contract and pushes it on every enabled delivery route.
3. The desk posts an alert on tiktok.live.started, holds the message id against the room_id, and closes that same alert when tiktok.live.ended arrives.
4. When a tracked video's file becomes fetchable, tiktok.media.ready carries the media URL so an archiving worker makes one request instead of a retry loop.

• A watchlist replaces a set of profiles someone was refreshing by hand, and live sessions surface while they are still open.
• Reposts keep their original author, so the desk can see whose video is spreading rather than crediting the creator who shared it.
• TikTok runs on the same account and event vocabulary as the desk's other sources, so adding it does not mean a second vendor or a second integration.

• TikTok delivery is described as sub-second in typical operation; that is an operating range, not an SLA, and no per-account millisecond figure is promised.
• This deployment monitors public creators only, and the feed is real-time with no historical backfill or queued replay while a client is disconnected.
• It is an event source, not an analytics suite: there is no follower reporting, engagement benchmarking or content-performance dashboard.

• Real-time TikTok monitoring API
• Get notified when a TikTok creator goes live
• Build a TikTok creator alert bot in Python