DEVELOPER API

SMS-Activate-compatible API

A drop-in SMS-Activate / HeroSMS API — keep your existing handler_api.php code, just swap the host and key.

Migrating off SMS-Activate (which shut down in December 2025) or off HeroSMS? You do not have to rewrite anything. Eveses runs a fully compatible handler_api.php gateway that speaks the same api_key / action / service / country protocol, so your existing client keeps working after a one-line change. When you are ready, the same account exposes a modern REST API with webhooks, typed SDKs, idempotency keys and automatic refunds.

How it works

1

Keep your code

Eveses implements the sms-activate `handler_api.php` protocol — `getNumber`, `getStatus`, `setStatus`, `getBalance` and friends all respond in the same format your current client expects.

2

Swap the host and key

Point your existing base URL at `https://api.eveses.com/stubs/handler_api.php` and drop in your Eveses `api_key`. No code rewrite, no downtime — run both providers in parallel and cut over per service.

3

Upgrade when ready

The same wallet and key also power the native REST API (`POST /v1/numbers/orders`), webhooks (push instead of polling), idempotency keys and automatic refunds for missed codes.

Code examples

Drop-in migration — the same handler_api.php protocol, just a new host and key.

# Before — SMS-Activate / HeroSMS
GET https://<old-host>/stubs/handler_api.php?api_key=OLD_KEY&action=getNumber&service=tg&country=0

# After — Eveses (drop-in: same protocol, swap host + key)
curl "https://api.eveses.com/stubs/handler_api.php?api_key=$EVESES_API_KEY&action=getNumber&service=tg&country=0"
# → ACCESS_NUMBER:12345:+380987654321

Pricing

Per-OTP pricing matches what SMS-Activate charged before it closed (from ~$0.05), and automatic refunds for missed codes lower your effective cost per delivered code. No subscription, no KYC.

See full pricing →

Integrations

ZapierMaken8nPostmanWebhooksRESTOpenAPI

Fire webhooks into Zapier, Make or n8n, or call the REST API directly.

OpenAPI & Postman

Import the OpenAPI spec or the Postman collection to generate a typed client in any language.

Open the spec →

FAQ

Is Eveses a drop-in replacement for the SMS-Activate API?›
Yes. Eveses runs an sms-activate-compatible handler_api.php gateway. Point your existing client at https://api.eveses.com/stubs/handler_api.php, swap in your Eveses api_key, and the same api_key/action/service/country protocol works unchanged — no code rewrite.
Does the compatible gateway work for HeroSMS code too?›
Yes — HeroSMS inherited the same SMS-Activate protocol, so any client written for either works against the Eveses gateway after swapping the host and key.
Which handler_api actions are supported?›
The common activation actions — getNumber, getStatus, setStatus, getBalance, getPrices — respond in the same format your current integration expects.
Can I migrate gradually?›
Yes. Run both providers in parallel and switch traffic per service or per country. Because only the host and key change, rollback is instant.
What do I gain by moving to the native REST API?›
Webhooks (push delivery instead of polling), typed SDKs for JS/Python/Go/PHP, idempotency keys for safe retries, a live pricing explorer, and automatic refunds when a code never arrives.

Related guides

Related APIs

Ship SMS-Activate-compatible API today

Create an account, grab an API key, and make your first call in minutes.

Get your API key