SIMUB activation API

Authentication and endpoint choice

Protected requests use the API key associated with your verified SIMUB account. Send it only over HTTPS and keep it in a server-side secret store or environment variable; never embed it in client code, a public repository or a screenshot. The SMSHub-compatible handler receives action as a parameter, while SIMUB SMS routes put it in the path. Choose one interface and parse its documented response format.

• Use /stubs/handler_api.php for an existing SMSHub-style client that sends action, api_key and action-specific parameters.
• Use /api/sms/{action} when a direct SIMUB SMS route better fits your server application.
• Use the dedicated /api/mail endpoints for temporary mail; SMS activation identifiers and mail identifiers are separate.

Discover services, countries, prices and balance first

Call getBalance for available funds, getServices or getServicesList for current service codes, and getCountries for supported country codes. Choose getPrices, getPricesV2 or getPricesV3 for the response shape your integration expects. Catalogs, counts and prices are provider snapshots: cache them briefly, display the returned price when relevant and revalidate before purchase. Never invent a code from a visible label.

Core SMS activation lifecycle

A purchase and a status check are different operations. Persist the activation identifier immediately so an application timeout does not lose a reserved number.

• Select a documented service and country, inspect current price and stock, then call getNumber, getNumberV2 or getNumberV3 once.
• Parse ACCESS_NUMBER:ID:NUMBER or the documented JSON equivalent and store the activation ID with your internal request reference.
• Poll getStatus with that ID. STATUS_WAIT_CODE means the request is still waiting; STATUS_OK:CODE contains a received code.
• Use setStatus only for a transition allowed by the reference: 1 ready, 3 request another SMS, 6 complete or 8 cancel. Do not reuse the number for another service.

Statuses, errors and uncertain requests

SMSHub-compatible actions can return text tokens, while newer routes may return JSON. Correct or rotate a BAD_KEY credential instead of retrying. BAD_SERVICE means an action or service is unsupported. NO_BALANCE requires funding; NO_NUMBERS means no matching offer is currently available; BAD_STATUS marks an invalid transition. After a timeout, reset or server error on getNumber, reconcile through the stored activation or status before purchasing again. A blind retry can create a duplicate reservation.

Flusso di attivazione e-mail temporanea

L’attivazione e-mail usa route separate e risposte JSON. Interroga getPriceRests, getPrices o getRests per servizi, domini, prezzi e disponibilità. Salva il mailId restituito da getActivation. Usa getStatus per lo stato e getCode per il codice ricevuto. setStatus e requestRefund devono rispettare lo stato corrente e la politica pubblicata. Una casella temporanea non è una casella permanente né un metodo sicuro di recupero.

Esempi di richieste sicure

I valori seguenti sono segnaposto volutamente non validi. Sostituiscili solo in un ambiente server protetto. Gli esempi curl inviano parametri codificati separatamente senza concatenarli manualmente in un URL.

• Saldo: curl --get 'https://api.simub.com/stubs/handler_api.php' --data-urlencode 'api_key=YOUR_API_KEY' --data-urlencode 'action=getBalance'
• Prenota: curl --get 'https://api.simub.com/stubs/handler_api.php' --data-urlencode 'api_key=YOUR_API_KEY' --data-urlencode 'action=getNumber' --data-urlencode 'service=tg' --data-urlencode 'country=0'
• Leggi stato SMS: curl --get 'https://api.simub.com/stubs/handler_api.php' --data-urlencode 'api_key=YOUR_API_KEY' --data-urlencode 'action=getStatus' --data-urlencode 'id=ACTIVATION_ID'
• Leggi stato e-mail: curl --get 'https://simub.com/api/mail/getStatus' --data-urlencode 'api_key=YOUR_API_KEY' --data-urlencode 'id=MAIL_ACTIVATION_ID'

Affidabilità, sicurezza e uso responsabile

Imposta timeout finiti, usa un backoff esponenziale limitato per il polling e fermati allo stato finale. Rimuovi api_key, numeri, indirizzi e codici dai log. Valida le risposte e limita gli acquisti simultanei. Disponibilità, reti e filtri cambiano: né la disponibilità né la consegna del codice sono garantite.