EnglishSell eSIMs and phone numbers to your own customers
SIMAREA is one account, one prepaid balance and one API. Top it up once, issue a key, and order from your own shop, bot or app. There is nothing to install and no contract to sign to start.
New here? This is what you would be selling
SIMAREA is one platform with two products: eSIM data plans and virtual numbers. One account holds both. One prepaid balance in US dollars pays for both, and you top that balance up with crypto.
Reselling here means buying from that balance with an API key. You keep your own shop, your own prices and your own customers. We supply the numbers and the data and we handle the delivery; you decide what the product looks like and what it costs. Every order your key places lands in the same account you can sign in to and read.
What you can sell
Two products, one sentence each. Each card opens the page that explains it properly.
eSIM data plans
Mobile data abroad with no plastic SIM card to post. Your customer picks a destination, pays by the day or by the plan, and installs it by scanning a QR code on a phone that supports eSIM.
See the destinationsVirtual numbers
A dedicated non-VoIP line, rented by the term. It is one number your customer keeps for as long as they renew it, it accepts messages from any service, and it keeps its whole message history.
See virtual numbers| Family | What your customer gets | Chosen by | On the API today |
|---|---|---|---|
| eSIM data plans | Mobile data on a phone that supports eSIM, installed from a QR code | The destination, and how long the trip is | Not yet — see the note below |
| Virtual numbers | A dedicated non-VoIP line that keeps every message it receives | The country, the service, and the term you rent it for | Yes — buy, read and cancel |
eSIM data plans are not on sale yet.
eSIM pricing depends on a question with our supplier that is not settled, so no data plan is priced and none is offered for sale — on the API or on the website. The package route works, your key authenticates, and the list it returns is genuinely empty. An eSIM purchase attempted today is refused and nothing is charged.
The destination list answers in full in the meantime, so you can build and test your destination mapping now and add packages on the day they are priced. Virtual numbers are buyable today. The API reference says the same thing next to the route itself.
How reselling works here today
No portal, no onboarding call, no separate system. Four plain facts, and none of them is something we are planning to build.
One ordinary account
There is no separate reseller sign-up and nobody to be approved by. You create the same free SIMAREA account a customer creates, and it becomes your reseller account the moment you issue a key.
One prepaid balance
You top it up in US dollars, with crypto. Everything you buy afterwards comes out of it — through the API and through the website alike. There is no invoice at the end of the month and no credit line to arrange.
One key per integration
You issue keys yourself, from the API keys panel inside your account. A key is shown once, when it is created, and cannot be read back — so store it before you close the dialog.
One HTTP API
Your shop, bot or app buys by sending a request. There is nothing to install beyond an HTTP client, no SDK you have to adopt, and no contract to sign before your first order.
Getting started
Four steps. You can do all four yourself, today, without talking to anybody.
Create an account
The same free SIMAREA account any customer creates. There is no reseller application, no minimum order and nothing to pay to open it.
Top up your balance
Add money once, with crypto. This one prepaid balance is what every purchase draws from afterwards — through the API and on the website.
Issue an API key
Open the API keys panel in your account and create one. The key is shown once and cannot be read again, so store it before you close the dialog.
Call the API
Send the key as a bearer token, read the catalog, and buy. The reference has every route, every error code and a working example to copy.
Why you can build a business on it
Every claim here is a property of the running system, not an intention. They are the things that decide whether an integration is safe to leave alone overnight.
The API spends the same balance you do
There is no separate reseller wallet to fund, reconcile or watch drift. The balance route reports the same prepaid balance the website spends, and a purchase that would overdraw it is refused before anything is bought — the refusal tells you the shortfall, so a top-up can be automatic.
An API order is an ordinary order
An order placed by your key is the same record as an order placed by hand on the site: same account, same order list, same messages, same cancel button. When a customer asks you what happened, you can sign in and look — you are not reading a copy of the truth.
Money cannot be mangled in transit
Every amount crosses the wire as whole cents inside a string, never as a JSON number, and every amount is US dollars. A JSON number is a floating-point value, and money does not survive one. Your client parses it once, on purpose.
A retry can never charge you twice
Every purchase must carry an Idempotency-Key header that you choose; a request without one is refused outright. Retry with the same key and the same order and you are handed the first order back with nothing charged. Reuse that key for a different order and the request is refused rather than guessed at.
Honest rules, including the one you would rather not read
None of these is buried. All five are enforced in code, so they behave the same way on a busy night as on a quiet one.
A failure refunds itself. A virtual number we cannot set up after you pay is refunded to your balance automatically — you do not have to notice it or ask for it. One canceled before any message has arrived is refunded the same way. One case is not refunded and we would rather you read it here than discover it: a rented number that ran its whole term is a completed sale, so canceling it returns zero rather than an error.
Rate limits belong to the key, not to the account. The limit is counted per key, per minute. Issue one key per integration and a busy hour in one of them cannot throttle the others — the bucket is named after the key, never after you. Every successful response tells you how much of your window is left and when it resets, so a well-behaved client never has to guess.
A revoked key stops on the very next request. Nothing about a key is cached anywhere, for any length of time — not for a minute, not for a second. That is a deliberate cost we pay on every single request, because "revoked immediately" quietly means "revoked when the cache expires" the moment anyone optimises it. Revoke a leaked key and it is dead, not dying.
We never name our suppliers. No supplier or carrier name appears in any field of any API response, so nothing you pass through to your customer can carry one. Which upstream fills an order is our problem to solve and re-solve; it is not something your integration has to model, and it is not something your customer ever reads.
There is no key in a URL, ever. The key travels in the Authorization header and there is no query-string alternative to fall back on. Query strings end up in web-server access logs, in browser history, in referrer headers on outbound links and in the error reports of every proxy in between — a key that lands in a log has already leaked.
Selling SIMAREA products is subject to our terms of use. If you would rather earn from sending us customers than from reselling to your own, the affiliate program is a different arrangement entirely: your reader buys from SIMAREA and you are paid a commission, so you fund no balance, set no price and answer no support question.
Who this is for
Anyone can integrate. These are the four shapes of business it fits most naturally.
Online shops and marketplaces
You already have a checkout and customers who trust it. Add numbers and data to what you sell and let your own order flow call ours, at whatever price you set.
Agencies and account teams
Teams who open and run many accounts on behalf of clients. One balance covers everyone, and every number and every message stays visible in one place instead of in a spreadsheet.
Bots and automation
A Telegram bot, a Discord bot or an internal script. Buying a number is one request and canceling it is another, so a bot can offer the whole product without a dashboard behind it.
SaaS products
Products that need a verification number inside their own onboarding, testing or QA. Buy one at the moment you need it, and get the charge back automatically when a code never arrives.
What we have not decided yet
There is no reseller price list, and we are not going to invent one.
Three commercial questions are still open: volume pricing, settlement terms and a support commitment. None of them has been agreed, so none of them is published here or anywhere else on this site. Everything above about how the product works is real and running. Everything about what a reseller pays does not exist yet.
You can still start today, at the ordinary prices you can already see on the site, and nothing about the API changes when the terms land. If you want to arrange something directly in the meantime, write to [email protected] and tell us what you plan to sell and roughly how much.
When the terms are agreed they will be published on this page and in our terms of use. Until then, please do not read this page as an offer.
Support, and what happens next
Write to [email protected]. Tell us what you want to sell, which of the two products you need, and where your customers are. That is enough for us to give you a useful answer rather than a brochure. If you already know you need something the standard setup does not cover, say so in the first message.
You do not have to wait for a reply to begin. Create the account, top it up, issue a key and read the reference. The API is live, and it buys through exactly the same code the website’s own buttons do — there is no second, lesser path for resellers, which is also why there is only one set of bugs to fix and one set of refunds to trust.
We have not agreed a response-time commitment, so we are not printing one. That is the same rule as everything else on this page: if it has not been decided, it does not appear here dressed as a promise.
Everything you need to start is already switched on
An account, a balance, a key and one HTTP API. The reference has every route, every error code and an example you can paste into a terminal.
Reseller questions
What is SIMAREA?
SIMAREA is one platform selling two connectivity products: eSIM data plans for mobile data abroad, and virtual numbers you rent as a dedicated line.
Both live in one account and are paid for from one prepaid balance in US dollars. That is true for a person buying one number on the website and for a business buying thousands through the API — it is the same account and the same balance.
How do I become a reseller?
You create a normal SIMAREA account, top it up, and issue an API key from the API keys panel inside that account. There is no separate reseller sign-up, no application to write and nobody to be approved by.
From that point your integration can buy. Nothing has to be installed on your side beyond an HTTP client, and there is no contract to sign before you start.
How do I pay for what I sell?
From your prepaid balance. You top it up with crypto, and every purchase your key makes is taken from it. There is no invoice at the end of the month and no credit line.
It is the same balance the website spends, so you can read it by signing in or by asking the API. If it is too low the purchase is refused before anything is bought, and the refusal tells you exactly how much you are short — which is enough to automate your own top-ups.
Is there a reseller discount, or a volume price?
Not yet, and we are not going to pretend otherwise. Volume pricing, settlement terms and a support commitment have not been agreed, so there is no discount schedule published on this page or anywhere else on this site. Anything you read here about how the product works is real; there is simply nothing yet about what a reseller pays.
You can start today at the ordinary prices you can already see, and nothing about the API changes when terms are agreed. If you want to arrange something directly in the meantime, write to [email protected] and tell us what you plan to sell and roughly how much.
Can I sell eSIM data plans through the API today?
No, not yet. eSIM pricing depends on a question with our supplier that is not settled, so no data plan is priced and none is offered for sale. The package route answers with an empty list on purpose — your key works, the route works, and the list is genuinely empty. An eSIM purchase attempted today is refused and nothing is charged.
The destination list does answer in full, so you can build and test your destination mapping now and add packages on the day they are priced. Virtual numbers are buyable today.
What stops a retry from charging me twice?
Every purchase must carry an Idempotency-Key header that you choose, and a request without one is refused. We do not generate one for you, and that is the point: a key the server invents is a fresh key on every attempt, so every retry would become a second order — which on this product means a second charge and a second number.
Send the same key with the same order again, after a timeout or a dropped connection, and you are handed the first order back with nothing charged. Send that same key with a different order and the request is refused rather than being answered with the earlier one. Retrying is always safe; a mistake is always loud.
What happens if an order fails, or no SMS ever arrives?
The charge comes back to your balance on its own. A virtual number we cannot set up is refunded automatically, and one canceled before any message arrived is refunded too. You do not have to open a ticket for either, and you do not have to be watching.
One case deliberately does not refund: a rented number that ran its whole term. That is a completed sale rather than a failure to deliver, so canceling it answers with a refund of zero instead of an error. A number that has already received its SMS cannot be refunded either — the code you paid for arrived.
Will my customers know the numbers come from somewhere else?
Not from us. No supplier or carrier name appears in any field of any API response, so nothing you pass through to your customer can carry one. We check for that with an automated gate rather than trusting ourselves to remember.
How you present the product is entirely yours to decide. We do not put ourselves in front of your customer and we do not contact them.
What should I do if a key leaks?
Revoke it from the API keys panel. Revocation takes effect on the very next request, because nothing about a key is cached — there is no window in which a revoked key keeps buying.
Issue one key per integration rather than sharing one everywhere, so revoking a leaked key takes down one integration instead of all of them. Rate limits are counted per key too, which means separate keys also stop a busy integration from throttling the rest.
Are there webhooks?
Not in this version. You poll the order you created, and every successful response carries your rate-limit window so you can decide how often to ask without guessing.
The order you read back is always current: it is re-read from the database rather than assembled from what was true a moment earlier, so a message that landed in between shows up.