To schedule holiday orders with an SMM API, you send one drip-feed order that splits the total into runs placed at a fixed interval. The quantity per run, the number of runs and the minutes between them decide when delivery happens. Plan backwards from the holiday date, check the service supports drip-feed, and keep enough balance for the whole order.
What do drip-feed, runs and interval mean in an SMM API?
Drip-feed is a way to split one order into several smaller orders that start one after another. Instead of sending the full amount at once, the panel places a part of it, waits, then places the next part.
Three values control this:
- Quantity: the amount placed in each run.
- Runs: how many times that quantity is placed.
- Interval: the waiting time between runs, usually in minutes.
The total amount is quantity multiplied by runs. For example, a quantity of 500 with 6 runs gives a total of 3,000, and you are charged for the total. Exact parameter names and accepted values are listed in the helnsocial API v2 documentation, so check them before you write code.
Drip-feed only works on services that support it. The services list with prices, min/max and refill options shows which ones do. The quantity per run must also sit inside the service's min and max.
Why schedule holiday orders instead of placing them on the day?
Holiday campaigns have a fixed date. Your client wants activity around a product launch, a sale or a seasonal post, not three days later.
Scheduling through the API means you build the plan once and let the panel place each run. You do not need someone awake at midnight to press a button. It also spreads the order over a period that matches the campaign, rather than one sudden jump.
For example, an agency running a Black Friday sale on 27 November 2026 might want engagement to build across the week before. One drip-feed order sent a few days earlier covers that window without manual work on the day.
How do you calculate runs and interval for a holiday window?
Start from the campaign window, not from the total amount. Decide when the first run should start and when the last run should be placed. Then work out how many runs fit and how far apart they are.
The basic formula is simple. The time span covered equals (runs minus 1) multiplied by the interval. The first run starts when the order is accepted, and the last run is placed after all the intervals have passed.
Here is a worked example for a client who wants 4,800 views on a Christmas video, spread over two days before 25 December 2026.
| Step | Decision | Result |
|---|---|---|
| 1. Total amount | Client wants 4,800 in total | 4,800 |
| 2. Window | Spread across about 48 hours | 2,880 minutes |
| 3. Runs | Choose 12 runs | 11 intervals between them |
| 4. Quantity per run | 4,800 divided by 12 | 400 per run |
| 5. Interval | 2,880 divided by 11, rounded down | about 261 minutes |
| 6. Check service limits | Is 400 between min and max? | Adjust runs if not |
These numbers are only for example. Real values depend on the service you pick, its min and max, and the average time shown in the services list. Keep in mind that the interval controls when each run is placed, not how fast each run is delivered.
What if the numbers do not divide evenly?
Quantity per run is the same for every run, so the total must be a clean multiple. For example, if the client wants 5,000 and you choose 12 runs, you get 416.67 per run, which will not work. Pick 10 runs of 500, or adjust the total slightly with the client before ordering.
How do you send a drip-feed order through the API?
A drip-feed order goes through the same add order call as a normal order. You add the run and interval values alongside the service ID, link and quantity. The API returns an order ID, which you store for status checks.
- Call the services endpoint and confirm the service supports drip-feed.
- Check your balance with the balance endpoint. The full total must be covered.
- Send add order with service, link, quantity per run, runs and interval.
- Save the returned order ID against your client's job.
- Poll status or multi status to follow progress.
For example, if you manage a small reseller site, your own system can map each client order to one drip-feed order ID. When the client asks for an update, you look up that ID instead of searching manually. If you are new to API calls in general, the guide on what an SMM panel API is and how to use it covers keys, requests and responses.
How do you check the link before a scheduled order starts?
The link on an existing order cannot be changed. If it is wrong, you need to place a new order. With scheduled holiday orders, this matters more, because a mistake may only show up days later.
For example, a client sends a link to a draft post that will be replaced by the final holiday post on launch day. If you order on the draft link, every run goes to the draft. Ask clients for the final, public link, and make sure the account or post is not private when the first run starts.
What do the order statuses mean during a drip-feed?
A drip-feed order passes through the same statuses as other orders. Explaining them clearly saves you many support messages from clients during a busy season.
| Status | What it means | What to tell the client |
|---|---|---|
| Pending | Received, not yet started | The order is queued |
| Processing | Sent to processing and usually waiting to start | Delivery has not begun yet |
| In progress | Delivery has started | Runs are being delivered |
| Partial | Part delivered, remainder refunded to balance | Some was delivered, the rest was credited back |
| Completed | Delivery finished | The order is done |
| Canceled | The charge returns to the balance | Nothing is owed for it |
A common mix-up is Processing. It does not mean delivery is underway. For example, a client who sees Processing on the evening of 24 December 2026 may think views are arriving. They are not yet, and setting that expectation early avoids a complaint.
How do start count and refill work on scheduled orders?
The start count is the counter when the order starts. Refill restores drops down to the start count plus the ordered amount, within the refill period shown on the service. If the count falls below the start count, no refill is done until the count is brought back up to the start count.
For example, a post has 1,200 likes when the order starts and you ordered 2,000. Refill can restore the count back toward 3,200 if it drops within the refill period. If the count falls to 1,000, which is below the start count, no refill is done until it is back at 1,200. On eligible completed orders you use the refill button in the dashboard or the refill call in the API.
For follower and engagement campaigns, add one note for your clients. Platforms set their own rules on what counts and how engagement is reviewed. Read the official policy of the platform before you promise a client any result.
How should you plan balance for a holiday season?
A drip-feed order charges the full total, not one run at a time. If the balance does not cover the whole order, it will not be accepted. During a season with many client campaigns, that adds up quickly.
For example, if you plan ten drip-feed orders for different clients across the week of 21 December 2026, add the totals together first. Then add funds once, before you send the batch, instead of topping up between calls. Your code can call the balance endpoint before each add order and stop if funds run low.
If an order ends as Partial or Canceled, the relevant amount returns to your balance. You can use it for the next order without any extra step.
When is a mass order better than drip-feed?
Drip-feed spreads one order over time. A mass order sends many separate orders at once, each with its own link. They solve different problems.
For example, a client with a twelve-day holiday series needs a small order on each new post. Each post has its own link, so a mass order or separate add order calls fit better. Drip-feed suits one link that needs activity spread across a window. You can also combine both: a mass order where each line is a drip-feed order, if the service supports it.
What this means for resellers and agencies
Holiday scheduling is mostly arithmetic and checking. Work backwards from the date, confirm drip-feed support and limits, collect final links, and cover the full total in your balance. Explain statuses and refill rules to clients before the season starts, and you will spend the busy weeks delivering rather than answering questions. If you are building this into a business, the guide on how to start an SMM reseller business covers the wider setup.
When you are ready to schedule, create an account and get your API key.
Frequently asked questions
Can I cancel a drip-feed order after some runs have started?
You can send a cancel request through the API or dashboard, but whether it is accepted depends on the service and the order's status. If a cancel goes through, the charge for the undelivered part returns to your balance.
Does the interval set how fast each run is delivered?
No. The interval only sets the waiting time before the next run is placed; delivery speed of each run follows the service's own average time.
Can I use drip-feed on every service?
No, only on services that support it. The services list and the services API endpoint show which ones do.