← All guides

2026-03-23 · smm reseller api errors, api bad link, api qty limits

Reseller API Errors: Fixing bad_link, qty Limits and Balance Fails

Integrating an SMM API? The errors every reseller hits in week one — and the exact fixes for links, quantities, drip and funds.

bad_link: validate before sending

Apply the incognito test server-side: your code should reject profile URLs where a post URL is required before the request leaves your server. Log the exact link you sent — half of 'API bugs' are string concatenation bugs on the reseller side.

Normalize first: strip tracking params, expand short links, force https. Providers compare dumb strings, not intentions.

qty limits: read min/max dynamically

Every service carries min and max, and they change when providers adjust capacity. Cache the service list, re-fetch at least hourly, and clamp user input client-side with a clear message.

Never hardcode limits into your frontend — one provider-side change turns every order into an error until your next deploy. Our reseller API exposes live limits per service for exactly this.

no_funds and duplicates

Pre-check balance before sending mass orders; a half-funded batch leaves you with partial deliveries and angry clients. And make mass requests idempotent on your side — one order ID per client request, retried safely.

For status tracking, poll with backoff (minutes, not seconds) and treat 'In progress' as normal for hours on gradual services.

Try it on your own numbers

Sign up and place your first order in two minutes.

Create free account

Keep reading