Most SMM API errors fall into a few groups: a bad API key, a wrong service ID, a quantity outside the allowed range, an incorrect link, or a low balance. Each error tells you which part of your request the panel rejected. Read the message, fix that one field, and send the request again.
This article explains each group in plain terms, so you can fix your own integration and explain the problem to a client. Error wording differs between panels and can change. The exact messages for helnsocial are listed in the helnsocial API v2 documentation. Treat that page as the source, not this article.
How does an SMM API report an error?
When a request works, the API returns the data you asked for. That can be an order ID, a status, or your balance. When a request fails, the response contains an error message instead, and no order is created.
For this reason your code should always check the response before saving anything. A common mistake is to store an empty order ID as if the order went through. Your client then waits for an order that never existed.
For example, say your script sends an add order request and gets back an error instead of an ID. Log the full response, mark the request as failed in your system, and show your client a clear message. Do not retry blindly in a loop.
If you are new to the API actions themselves, the guide on what an SMM panel API is and how to use it covers the basics first.
What does an invalid API key error mean?
This error means the panel could not match your key to an account. Nothing in the request is processed until the key is accepted. So this check comes before service, quantity or link checks.
The usual causes are simple. The key was copied with a missing character or an extra space. Or the key was regenerated in the dashboard and the old one is still in your code.
- Copy the key again from your account page.
- Check for spaces or line breaks before and after it.
- Make sure the key is sent in the field the documentation names.
- If you run several sites, confirm each one uses the current key.
For example, if you regenerate your key after a staff member leaves, every script using the old key will start failing at once. Update all of them in the same session.
Why does the API say a service is not found or not available?
This error means the service ID in your request does not match an active service. The ID may be mistyped. More often, the service was disabled or replaced, and your stored list is out of date.
Services lists change over time. Prices, min and max quantities, and refill options can all be updated. If your own panel or store copies the list once and never refreshes it, you will sell services that no longer exist.
For example, a client orders service 1234 through your store, but that ID was retired last week. The API rejects it. The fix is to call the services action on a schedule, compare it with your saved list, and hide anything that has disappeared. You can also check the live services list with prices, min/max and refill options by hand.
What causes a quantity error?
A quantity error means the amount you sent is below the minimum or above the maximum for that service. Every service has its own range. The range is shown in the services list and returned by the services action.
These errors often come from your own store settings. You may allow clients to type any number while the service has a fixed range. Or the range changed and your store did not update.
For example, if a service has a minimum of 100 and your client enters 50, the order fails. Add a check in your form that uses the current min and max for that service ID. Then the client sees the limit before paying you.
Drip-feed and quantity
Drip-feed orders split delivery into runs. The quantity per run still has to fit the service rules. Drip-feed is also only available on services that support it, so sending drip-feed fields to another service can cause an error.
What does an incorrect link error mean?
This error means the link does not fit what the service expects. A service for post likes needs a post link. A service for followers needs a profile link. A private account or a deleted post can also cause trouble.
Ask your clients for the exact link type before they order. Short links, links with tracking parameters, or app share links sometimes do not match the format a service needs.
One rule matters here. The link on an existing order cannot be changed. If an order was placed with the wrong link and accepted, the only fix is a new order with the correct link.
For example, a client pastes their profile link into a post views service. If the order is accepted, it cannot be edited later. Build a simple link check into your order form so this is caught before it reaches the API.
Why do I get a not enough funds error?
This error means your balance is lower than the cost of the order. The API checks the price of the service times your quantity against the balance on your account. If the balance is short, the order is not created.
You can avoid most of these errors by calling the balance action before large or mass orders. If the balance is low, add funds through the dashboard first.
For example, a reseller sends a mass order of many links at night. The first orders go through, then the balance runs out and the rest fail. Check the balance before the batch starts, and log which links failed so you can resend only those.
What errors come back on status, refill and cancel requests?
These actions work on orders that already exist. Errors here usually mean the order ID is wrong, belongs to another account, or is not in a state that allows the action.
Refill errors
A refill request can be refused for several reasons. The service may not have refill. The refill period shown on the service may have ended. The order may not be completed yet.
Refill also has a clear limit. It restores drops down to the start count plus the ordered amount, within the refill period. 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, an order starts at a start count of 1,000 and orders 500, so the target is 1,500. If the count falls to 1,400, a refill can cover that gap. If it falls to 900, refill covers up to 1,500 but not losses that took the count under 1,000 from the client's own existing audience.
Cancel errors
Cancel is not possible on every order. If delivery has already started, or the service does not support cancel, the request is refused. When a cancel does go through, the status becomes Canceled and the charge returns to your balance.
Which order statuses look like errors but are not?
Some statuses confuse clients, even though nothing has gone wrong. Explaining them early saves you support tickets.
- Pending: the order was received but has not started.
- Processing: the order was sent to processing and is usually waiting to start. It does not mean delivery is underway.
- In progress: delivery has started.
- Partial: part of the order was delivered. The undelivered remainder is refunded to your balance.
- Canceled: the order was canceled and the charge returned to your balance.
For example, a client sees Partial and thinks they lost money. You can show them that the undelivered part went back to the balance, and offer a new order for the rest if they want it.
Quick reference: error, cause and fix
| Error type | Likely cause | What to check | What to tell your client |
|---|---|---|---|
| Invalid API key | Typo, extra space, or old key | Copy the current key from your account | A technical issue on our side, being fixed |
| Service not found | Wrong or retired service ID | Refresh your services list | This service is no longer offered, here are alternatives |
| Quantity out of range | Below min or above max | Current min/max for that service | Please choose an amount within the limit shown |
| Incorrect link | Wrong link type or private page | Link format the service expects | Please send the exact post or profile link, set to public |
| Not enough funds | Balance below order cost | Balance action before the order | Usually nothing; top up and resend |
| Refill refused | No refill, period ended, or not completed | Service refill period and order status | Refill covers drops to start count plus ordered amount, within the period |
| Cancel refused | Delivery started or not supported | Order status and service options | The order is already running and will continue |
How should you log API errors for your own clients?
Keep a simple log of every request that fails. Save the time, the action, the service ID, the link, the quantity and the full error response. This lets you see patterns, such as one service ID that keeps failing.
Good logs also make support faster. When you contact support, which answers in English, send the order ID or the request details and the exact error text. That is much quicker than a description from memory.
For example, if several clients report the same failure in one afternoon, your log may show they all used an outdated service ID. You fix one line in your list instead of answering each ticket separately.
What this means for resellers and agencies
Most API errors are caught before money moves, so they protect your balance rather than cost you. Validate service IDs, quantities and links in your own forms, and check your balance before mass orders. Then the errors your clients see become rare and easy to explain.
When you are ready to connect your store or panel, create an account and get your API key.
Frequently asked questions
Where can I find the exact error messages the helnsocial API returns?
The exact wording is in the API v2 documentation at helnsocial.com/api. Always build your error handling from that page, since wording can change.
Am I charged when an add order request returns an error?
No order is created when the API returns an error, so there is nothing to charge. If you are unsure, call the status or balance action to confirm.
Can I fix a wrong link by editing the order through the API?
No. The link on an existing order cannot be changed, so you need to place a new order with the correct link.