Viewer Configurator API

No. It is the same key as for the shop API, from “API settings”. The endpoint and the way to pass it differ: here it is the Authorization header, in the shop API — the key parameter.

Pass the key without Bearer, account number or spaces. Make sure the key is saved in settings and has not been changed since. A 400 response means the header never arrived: some proxies and hosting providers strip Authorization.

There is no sandbox. /user/info, the reference lists and /helper/calculator are safe to try: they charge nothing. Only POST /order and PUT /renew charge money.

The reference lists work. 404 with [] means the address was not recognised: check the full path, e.g. /configurator/api/helper/platforms, and the GET method. Still failing — send support the address, request body and server response.

Both come from “API settings”. If no currency is selected — USD.

The configurator API covers Twitch, Kick, YouTube and VK Video Live. Viewers for other platforms, Trovo included, are catalog services ordered through the shop API.

Duration is counted in one unit and the remainder is dropped: 10 days is 1 week. Allowed: 1–5 days, 1–2 weeks, 1–2 months of 28 days. See the duration table.

The pause between viewers joining, in seconds. interval: 1 means 60 viewers a minute; with 100 viewers and interval: 2 everyone joins in about 3 minutes 20 seconds. The longer the pause, the more natural the online growth.

spread_percent is the share of viewers who leave and come back, so the online count is not a flat line. spread_delay is the pause between such swings, 120–900 seconds. Order creation used to take minutes (2–15) here — such values still work: anything below 60 is read as minutes. If you set spread_percent, pass spread_delay too.

views.retention — how many seconds a viewer watches before leaving and joining again. views.views_per_viewers — views per hour from one viewer. We advise no more than 5–10: higher growth looks unnatural.

Authorized viewers are logged into Twitch or VK accounts: they show up in the chat viewer list, and on Twitch they can collect channel points (is_collect_points). For now points only accumulate; spending them is planned. Unauthorized viewers count towards online but are not in the chat list.

“Individual viewers” for channels in casino and crypto categories, and for channels that drop out of categories and recommendations when boosted (shadow ban). Different servers and different geo. +45 % to price.

raid.count — raids per order (set at purchase, up to 10,000), raid.time — how many seconds viewers stay on the other channel after the raid, raid.viewers_percent — the share of viewers that go on the raid. A raid starts by itself when the streamer runs the raid command in chat. Raids are paid: the first one raises the price noticeably, each next one costs less. A raid does not extend the order: when order time runs out, viewers leave, even mid-raid. Turn off subscriber-only chat during the stream: with it on, a raid may fail.

Choosing a country does not change the price. The price depends on views, retention, authorization, floating viewers, raids, is_casino, Kick quality and subscription. The calculator shows the total.

The quality of viewer accounts. HQ costs 66 % more than MQ, UHQ — 133 % more.

Viewers join only a live stream. Make sure the stream is online, the order is not paused or stopped (is_freez, is_stop), free_time is above zero and the channel is correct. If all is fine, contact support and send the uuid.

No, the configurator works with live streams. VOD and clip views are separate catalog services ordered through the shop API.

On pause (is_freez) order time is frozen, but pause time is limited — see limits. On stop (is_stop) viewers leave and time keeps running. Need a break between streams, or bought in the morning for an evening stream — use pause (if actions contains pause).

PATCH /order/{uuid} with a new channel. Without a subscription the number of changes is limited and allowed once a day at most; the remaining count is shown in the Viewer Panel. In a subscription channels change freely.

Without a subscription one channel works: only the first item of channels is used. In a subscription — up to 100 channels, each with its own maximum; viewers are split between the channels that are live right now.

For the quote and order creation the viewers, views and raid blocks are shared, at order level next to type. When editing (PATCH) they are set per channel — inside channels[], as in the example.

Yes, within your plan and without a restart: change maximum via PATCH — down and back up to the purchased amount. More than you bought — only with a new order.

Renew in advance: PUT /order/{uuid}/renew while free_time is above zero. A finished order cannot be renewed — a new one with the same settings is created: check is_new and store the new uuid. The API has no auto-renewal.

POST /orders with {"filter": {"order_id": [7712345]}}. The number is a number, not a string.

There are no webhooks — you poll for the state. No more than 3 requests per second; once a minute is enough for statuses. Poll the list via /orders rather than each order separately. One order can be changed at most once every 10 seconds.

Prices are dynamic and can change. total_amount — what will be charged, total_base — base price without discounts and markups. To avoid overpaying pass max_total_amount: if the order turns out more expensive, you get 409 and nothing is charged. Minimum quantity and duration are visible in the Viewer Panel.

Response 400 with “Insufficient funds on balance” in message (error_user_credit). No order is created. Money and bonus points are counted together.

Promo code — in the coupon field. Bonus points are part of the balance and are spent together with money if the service accepts them.

Yes, it is the same list. Orders created in the Viewer Panel are available through the API as well.