How to Add a Provider to Your SMM Panel: Step-by-Step API v2 Setup
Add an API v2 provider to your SMM panel script: API URL and key, importing services, mapping IDs, setting prices, test orders and fixes for common errors.
To add a provider to an SMM panel, open your script's provider settings, enter the provider's API v2 URL and your API key, and check that the balance loads. Then import the services you want, map each to your own service, set your prices and place small test orders before switching anything on for customers.
Panel scripts differ in layout and naming, but the steps are the same everywhere because providers share the standard API v2 format. If you want to know what happens underneath each step, our guide to the SMM panel API walks through the actions and their answers.
What do you need before you start?
- An account with the provider. On Orbismm, every account can use the API from day one, with no deposit, monthly, setup or API fees.
- An API key with the right scopes. Reading services, statuses and balance needs
read; placing orders, refills and cancels needsorders. A key for a panel script needs both. - Your server's IP address, if you want to limit the key to it with an IP allowlist.
- A test key, for a first run without real money. Orbismm test keys start with
orb_test_, live keys withorb_live_. - A short list of services you plan to sell. Importing an entire catalogue makes mapping and support harder.
How do you add an API v2 provider, step by step?
- Create the key. On Orbismm: in the panel, open API and webhooks, create a key, give it the
readandordersscopes and copy it once. - Add the provider. In your script's admin, find Providers (sometimes API providers or Suppliers) and add one. Enter the API URL
https://orbismm.com/api/v2and paste the key. If the script asks for a type, choose the standard or v2 option. - Check the connection. Most scripts show the provider balance after saving. A number means the URL and key work; an error message means they don't (see the table below).
- Import services. The script calls the
servicesaction and lists each service with itsserviceID,name,category,rate,min,maxand therefill,cancelanddripfeedflags. Import only what you will sell. - Map IDs. Link each provider service ID to a service on your panel. If you already sell that service with another provider, switch its provider here rather than creating a duplicate.
- Set your prices. Add your markup on top of the provider rate per 1,000 (more on this below).
- Match limits and flags. Keep your minimum and maximum inside the provider's, and turn on refill, cancel and drip-feed buttons only where the provider's flags are true.
- Test. Place orders with a test key, or small real ones, on every mapped service. Watch each one reach a final status in your panel.
- Switch on status sync. Make sure the script's scheduled job (often a cron) runs, so statuses, remains and refunds flow back to your customers.
| Provider field (API v2) | Where it goes in your panel |
|---|---|
service | The provider service ID on your mapped service |
name, category | Your own service name and category; rename freely |
rate | Your cost per 1,000 in USD; your selling price is built on it |
min, max | Your order limits, equal to or inside these |
refill | Whether your customers see a refill button |
cancel | Whether your customers see a cancel button |
dripfeed | Whether you offer runs and interval on this service |
How should you set prices on imported services?
The rate from the provider is your cost per 1,000, already at your tier; on Orbismm that is Standard, or 5% off on Pro from $500 and 10% off on Business from $2,500 of spend over the last 30 days. Most scripts let you add a percentage or a fixed amount on top. For example, with a hypothetical rate of $1.20 per 1,000:
| Markup method | Your price per 1,000 | When cost changes to $1.30 |
|---|---|---|
| Percentage, +50% | $1.80 | Follows to $1.95 |
| Fixed, +$0.60 | $1.80 | Follows to $1.90, margin shrinks as a share |
| Manual price | $1.80 | Stays at $1.80 until you edit it |
Percentage markups are the safest default. Whatever you choose, re-sync services on a schedule. On Orbismm, price cuts apply immediately and increases are announced at least 48 hours ahead in the panel and by webhook, and the price of each order is fixed when placed. If your panel sells in another currency, remember that provider rates are in USD.
What are the common errors when connecting a provider?
API v2 returns errors as JSON with an error field and HTTP 200, which is what panel scripts expect. These are the messages you will meet most during setup, exactly as Orbismm sends them:
| Error | Usual cause | Fix |
|---|---|---|
Invalid API key | Typo, extra spaces, or a key that was revoked | Paste the key again, or create a new one |
This IP address is not allowed for this API key | The key has an IP allowlist and your server's address isn't on it | Add the server's outgoing IP to the allowlist |
This API key is not allowed to do that | The key lacks the orders scope needed for add, refill or cancel | Create a key with read and orders |
Incorrect service ID. | The mapped ID is wrong or the service is paused | Re-import services and check the mapping |
Incorrect link. | The link sent was empty or too long | Check how your panel passes the link field |
Quantity must be between … and …. | Your limits are wider than the provider's | Bring your min and max inside the provider's |
This service does not support drip-feed. | Runs and interval sent for a service without drip-feed | Turn drip-feed off on that service |
Not enough funds on balance. | Provider balance is lower than the order | Top up the provider balance |
Incorrect order ID | A live key looking up a sandbox order, or the reverse | Use the key the order was placed with |
API v2 has no protection against duplicates: the same add sent twice places two orders. If your script retries on timeouts, check its retry setting, or use API v1 with an idempotency key for custom integrations.
How do you know the integration is ready for customers?
- Every mapped service has completed at least one test order end to end.
- A partial or canceled order refunded your customer's balance on your panel, not just yours on the provider.
- Refill and cancel buttons appear only where the provider supports them.
- Statuses update on their own, without you pressing sync.
- You know where to look when an order stalls: on Orbismm, the order log shows moves to a backup line and every refund.
For a structured test with every status covered, follow SMM panel API testing with a sandbox. The full reference for each action is in the API v2 docs.
From Orbismm order data
From Orbismm order data: the API serves 0 services, and across still being measured orders in the last 30 days the median start time was still being measured.
Create a test key and connect your panel using the [API v2 reference](/docs/v2).
Frequently asked questions
- Do I need to know how to code to add a provider to my SMM panel?
- No. Panel scripts that support providers only need the API URL and your key. Coding is needed only if you build your own integration instead of using a script.
- What API URL do I use for Orbismm?
- Use https://orbismm.com/api/v2 with your API key. It works with any panel script that supports standard API v2 providers.
- Why does my panel say Invalid API key?
- The key was mistyped, copied with extra spaces, or revoked. Paste it again or create a new key in the panel.
- Can I test the connection without spending money?
- Yes. Use a test key: it runs the same calls with play money, and orders move through their statuses without reaching a supplier.
- Will my prices update when the provider changes its rates?
- Only if your script re-syncs services. On Orbismm, increases are announced at least 48 hours ahead in the panel and by webhook, so a scheduled re-sync keeps you ahead of them.