Building TikTok LIVE Alerts: Catch Creators the Moment They Spike

Why the spike is the moment to act

Recruiting is mostly a timing problem. A creator you message on a quiet afternoon has no reason to pay attention, and a creator you find weeks after their best month may already be signed. A creator who is spiking right now is different on every count. They are at their desk, their audience is engaged, and they have just proven to themselves that LIVE can earn. That is the rare window where a good message about growing further actually lands, because the creator is feeling the upside in real time.

The problem is that these moments are invisible unless you are watching constantly. No human can sit on a ranking board refreshing it all day, and by the time a spike shows up in yesterday's numbers it is over. An alert solves this by doing the watching for you and interrupting a person only when something worth acting on is actually happening.

The signal to build the alert on

A spike alert is only as good as the signal underneath it. You do not want to alert on follower count, which barely moves during a stream, or on raw viewer numbers, which are noisy. You want the thing that maps to money: a sudden jump in diamonds over a short window. That is exactly what a HOT signal captures. It flags creators whose gifting is surging right now, across every division of a country, and refreshes every few minutes so the flag reflects the current moment rather than a stream that ended an hour ago.

The RnG API exposes this as a hot endpoint that returns the creators spiking in diamonds at that instant. Whatever source you build on, the property to insist on is recency: a spike flag is worthless if it lingers after the stream is over, because your alert would fire a recruiter at a creator who has already gone dark.

What a poll returns

The core of the alert is a small job that asks the hot endpoint for the current spikes on a schedule. A single poll is one request:

curl "https://rngrow.com/api/v1/leagues/hot?country=RO" \
  -H "X-API-Key: rng_live_YOUR_KEY"

Each creator in the response carries the fields you need to decide whether to alert: the username and display name, the division they spiked in, how many diamonds they gained, their current score and follower count, and a hot_since timestamp marking when the spike began. That last field matters more than it looks, because it is what lets you tell a fresh spike from one you already saw on the previous poll.

Turn a stream of events into clean alerts

The fastest way to make an alert useless is to fire it every time a creator appears in the response. Because the endpoint refreshes on a short cycle and a spike lasts several minutes, the same creator shows up on poll after poll, and a recruiter who gets five pings about one creator quickly learns to ignore all of them. The fix is to remember what you have already alerted on and only fire once per spike.

A stable key does this cleanly. Combine the creator's username with theirhot_since timestamp, and treat that pair as the identity of a single spike event. Keep a short-lived record of the keys you have already sent, and skip any creator whose key you have seen. When the same creator spikes again on a later night, thehot_since value is new, so it counts as a fresh event and alerts again, which is exactly what you want. That single discipline turns a noisy feed into one clean message per genuine spike.

Confirm the creator before you fire

A spike tells you a creator is earning. It does not by itself tell you they are worth an immediate message, so it is worth adding one cheap check before you interrupt a person. Resolve the handle in real time and confirm they are still live, because a spike that just ended is not an outreach opportunity. A resolve call answers whether the profile exists, who it is, and whether they are live at that second, taken from the room's own state rather than a stale identifier.

You can also filter on the data already in the spike event. If your agency only recruits above a certain follower size, or only in specific divisions, drop the events that do not match before alerting anyone. The goal is that every alert a recruiter receives is one they would actually act on, because an alert that cries wolf is worse than no alert at all.

Find the creators who spike again and again

A live alert catches the moment, but the moment is not the whole story. A creator who spikes once might be having a lucky night. A creator who spikes repeatedly is a consistent earner, and that is a much stronger recruiting target. A history of past spike events, kept for a window of days, lets you separate the two. Pull the recent history for a country, group the events by creator, and the handles that appear over and over are your priority list.

This turns a real-time alert into something more durable. Instead of only reacting to tonight's spike, you build a standing shortlist of creators who reliably earn, ranked by how often and how hard they spike. A recruiter can work that list deliberately during the day and still get interrupted for the genuinely urgent breakout happening right now.

There is no webhook, so poll well

Be honest with yourself about the shape of this data. There is no push notification or webhook that tells you the instant a creator goes hot, so your alert works by polling, and polling well is the whole craft. Match your interval to how often the signal actually refreshes: checking every few minutes captures spikes without wasting requests, while hammering the endpoint every few seconds tells you nothing new and burns your budget.

Build for the rate limits from the start. Read the rate limit headers on each response, and when you get a 429, back off and wait for the interval the response asks for before retrying. If you watch several countries, stagger their polls rather than firing them all at once. A well-behaved poller running quietly in the background is the whole engine here, and it costs almost nothing once the timing is right.

Wire the alert to an action

An alert is only useful if it lands where a person will see it and act. The simplest build posts each confirmed spike to a team chat channel with the creator's handle, follower count, and a link to their profile, so whoever is on outreach can open it and message the creator in seconds. From there you can get more ambitious: enrich the alert with the creator's spike history, route different divisions to different recruiters, or feed the handle straight into whatever outreach flow your team already runs, whether that is a follow-up tool like Auto-Messenger or a recruiter working by hand.

The point is to shorten the distance between the spike and the message. Every minute between a creator's breakout and your outreach is a minute for someone else to notice them, so the whole system earns its keep by making the reaction fast and nearly automatic.

The takeaway

Catching creators the moment they spike is one of the highest-leverage things a recruiting team can automate, and it is not a large build. Alert on a real-time diamond signal rather than vanity numbers, deduplicate on the creator and the spike's start time so each event fires once, confirm the creator is still live before you interrupt anyone, and lean on spike history to find the repeat earners worth chasing deliberately. Respect the fact that you are polling, not receiving webhooks, and space your checks to match the refresh. Do that, and a recruiter no longer hunts for breakout creators. The breakout creators arrive in the team chat the moment they pop.