In most cases, API issues come down to a few simple things: wrong API URL, invalid key, incorrect service ID, or cron not running. Follow this step-by-step checklist and you’ll usually find the problem in a few minutes.

1. Confirm the Real Symptom

First, confirm what is actually happening inside dvScripts:

• New orders stay in Pending and never move to “In progress / Processing”.
• Orders show as “In progress” in dvScripts, but provider dashboard shows nothing.
• Order logs show API error messages but you never checked them.

Go to your dvScripts admin → Orders → open a recent order and check if there is an API log / response section. This will tell you what the provider answered (if anything).

2. Make Sure the Provider Is Actually Working

It sounds obvious, but sometimes the provider is down or has disabled the service.

• Login to your provider’s panel.
• Check their service list – is the service still active?
• Check your provider balance – zero balance = zero orders.
• See if they posted any status / maintenance messages.

If the provider is offline or your balance is empty, refill / wait, then test again.

3. Verify API URL & API Key in dvScripts

Most “API not sending” issues come from wrong URL or invalid key.

1. Open dvScripts admin → Providers.
2. Edit the provider that is not sending orders.
3. Compare:
   • API URL in dvScripts vs the URL in provider docs.
   • API key / token in dvScripts vs what you see in provider account.
4. Make sure there is:
   • No extra spaces before/after the key.
   • No typo in https://, domain or /api/v2 path.

After saving, place a small test order (e.g. minimum quantity) to confirm if the provider now receives it.

4. Check Service Settings (Service ID, Type, Min/Max)

Even if provider settings are correct, a wrong service configuration will stop orders from going through.

1. In dvScripts admin → Services, edit the affected service.
2. Confirm the Provider Service ID matches exactly the ID from provider.
3. Check the service type (e.g. Default, Package, Custom Comments, Mentions, etc.) matches the provider’s type.
4. Ensure your Min / Max quantity is within the provider’s allowed range.
5. If the service uses custom comments / usernames, make sure the field type in dvScripts matches what the provider expects.

If any of these are wrong, the provider may return an error and dvScripts will not create the order remotely.

5. Read the API Response Logs

dvScripts can store what the provider replies. Use this to see exactly what’s going wrong.

1. Open a failing order in dvScripts admin.
2. Look for an API log / response section (or a log page if your version has it).
3. Common messages you might see:
   • Invalid API key – key is wrong or disabled.
   • Service not found – service ID doesn’t exist at provider.
   • Not enough funds – top up provider balance.
   • Quantity is too low / too high – adjust min/max in dvScripts.

Fix the root problem based on the error, then re-test with a small order.

6. Make Sure Cron Jobs Are Running

If cron is not running, dvScripts may not send orders or update them with provider status.

1. Log in to your cPanel → open Cron Jobs.
2. Verify your dvScripts cron command is added, for example:

   php -q /home/username/public_html/cron.php

3. Check the schedule (e.g. every minute or 5 minutes, as recommended by dvScripts).
4. Save or correct the cron job if needed.

After fixing cron, wait a few minutes and see if pending API orders start to move.

7. Check Rate Limits & IP Restrictions

Some providers protect their API with rate limits or IP rules.

• Check provider docs for rate limits (e.g. X requests per minute).
• If they use IP whitelisting, make sure your server IP is added.
• If you recently migrated hosting, update the IP with your provider.

If your IP is not allowed, the provider may silently block or return generic errors.

8. Place a Clean Test Order

After updating settings, always test with a fresh, small order:

1. Create a simple service (for testing only) pointing to the same provider and service ID.
2. Set a low price and minimum quantity (within provider limits).
3. Place an order from your own account using a real link/username.
4. Check:
   • Order status in dvScripts.
   • Whether the order appears in the provider panel.
   • Any new API logs returned.

9. When to Contact Provider vs dvScripts Support

Contact your provider if:

• Your API URL + key are correct, but they still return strange or empty responses.
• Orders appear in dvScripts but not in their system, even with correct service IDs.
• They recently changed their API version / parameters.

Contact dvScripts support / your developer if:

• You see PHP errors or fatal errors in logs.
• You recently edited core files or custom modules and API stopped working.
• You need help reading error logs, cron configuration, or advanced debugging.

Once your provider API is working correctly, dvScripts will automatically push new orders, track status updates, and keep your panel running on autopilot – so you can focus on marketing, not manual order forwarding.