GetSMS.ONLINE

What do Tool Span Credits charge?

Tool Span Credits are required to use the service, and the provider gives a starting price and balance on its homepage. The homepage says reuse of a number for the same service costs less than its initial use. The following payment statements differ by source:

• Homepage — paid numbers start at $0.05 per verification; major cryptocurrencies accepted; $5 starting balance — checked 2026-10-31.
• Refund policy — all payments use cryptocurrency, and confirmed payments are final and non-refundable — checked 2026-10-31.
• Terms — payment methods may include credit or debit cards and certain cryptocurrencies — checked 2026-10-31.

Refund language also differs across the provider’s documents: the terms say credit or monetary refunds are assessed case by case, while cryptocurrency purchases may not be refunded. The terms also exclude refunds for users who cancel, and the refund policy calls confirmed payments final and non-refundable. Before adding funds, ask which payment methods apply to your account and how the refund clauses interact.

Which SMS services can one request name?

A single request can specify up to 5 service names, according to the API reference; the homepage lists more than 700 supported services. The service offers mobile and VoIP numbers, and says new numbers are added hourly.

The provider also offers dedicated virtual numbers that are not shared with others. For a one-time MDN request, the limit is one SMS; numbers are temporary and may not always be available. Availability figures returned by the `list_services` command are approximate rather than calculated in real time, according to the API documentation.

Which questions belong with support?

Ask support to reconcile the payment-method statements before choosing how to fund the account. The homepage names major cryptocurrencies, while the terms say payment methods may include cards and certain cryptocurrencies; the refund policy says all payments use cryptocurrency.

Ask how the case-by-case refund wording applies alongside the policy’s final-payment language, and what evidence support needs to review a claim about an unrelated SMS. The provider says such reports can be submitted through a support ticket with the number used and selected service.

For implementation planning, ask which setup requirements apply to the web interface and API. The documentation says API key generation requires email confirmation, but support can clarify what else your intended workflow needs.

How do API requests reach an SMS?

The documented API flow starts with generating an API key on the Account → Profile page and confirming the action by email. The API supports number requests, message and code retrieval, order-status checks, and verification automation, according to the provider’s documentation.

For status checks, the documentation recommends waiting at least 15 seconds between polling requests and says SMS polling is not recommended because it may consume substantial resources. The `read_sms` command returns at most 3 latest messages received in the past 2 days.

A configured webhook must return HTTP 200 without redirects. If its URL is unavailable, the script retries five more times at 10-minute intervals before stopping, according to the API documentation. The provider also lists a Python API client on GitHub.

Which stated conditions aid planning?

The provider states that users do not pay when a verification code does not arrive. This condition is useful to confirm against the specific request and account terms before relying on it.

The API documentation covers number requests, message and code retrieval, order status, and verification automation. Dedicated virtual numbers are listed as an option not shared with others.

The provider says reuse of a number for the same service costs 50% less than its initial use. It also says support typically replies within 12 hours; this is the provider’s stated response window, not a guarantee of resolution.

Which limits narrow number use?

The refund policy excludes cryptocurrency deposits, unused balance, token or network selection mistakes, third-party verification failures, and external-site account rejections.

• One-time MDN requests receive only one SMS, and numbers are temporary and may not always be available, according to the API documentation and terms (checked 2026-10-31).
• Free numbers are shared, and their incoming messages are public, according to the homepage (checked 2026-10-31).
• Account credentials and information cannot be shared; users also may not share provided phone numbers with third parties, according to the terms (checked 2026-10-31).
• Users must meet the service’s minimum age, and illegal conduct is prohibited, according to the terms (checked 2026-10-31).
• The terms disclaim continuous, uninterrupted, or error-free availability, according to the terms (checked 2026-10-31).

The provider says refund-system abuse, false claims, or fraud may result in permanent account suspension. See “What we could not confirm” for other details that affect evaluation.

Which SMS terms should comparisons match?

Compare SMS services by country and sender-ID coverage, per-message pricing, API behavior, delivery reporting, stated compliance terms, and support. In general, matching these criteria makes differences in coverage, costs, and implementation easier to assess.

Who can work within verification-only terms?

The service fits a workflow limited to requesting a number and receiving a verification code, provided the user accepts its terms. The provider defines its scope as verification only, ending when the code arrives.

Users must not share account credentials or provided phone numbers with third parties, and illegal conduct is prohibited. The vendor also says it is not affiliated with or endorsed by mentioned services unless it explicitly states otherwise.

What we could not confirm

• Integrations and setup requirements
• Countries covered
• Sender-ID rules
• Delivery reports and their availability
• Compliance statements beyond the prohibition on illegal conduct

What do the API and refund rules answer?

What happens if a verification code does not arrive?

The provider states that users are not charged when a verification code does not arrive. This is the provider’s stated condition; the refund policy separately excludes cryptocurrency deposits and unused balance. Check how the no-code condition applies to the payment and request type you plan to use.

How does the provider review an unrelated SMS?

The provider reviews an unrelated SMS manually, case by case, according to its refund policy. Customers can report an incorrect or unrelated SMS by submitting a ticket through the Support icon and including the number used and selected service, according to the refund policy. Approved credits are added to the account balance, according to the refund policy.

What does generating an API key require?

The API key must be generated on the Account → Profile page, and the action requires email confirmation, according to the API documentation. The documentation also recommends waiting at least 15 seconds between status polling requests.

What does a one-time request receive?

Each one-time MDN request can receive only one SMS, according to the API documentation. A single request can specify up to 5 service names. Availability data from `list_services` is approximate and is not calculated in real time.

How should a configured webhook respond?

A configured webhook must return HTTP 200 and must not use redirects, according to the API documentation. If the webhook URL is unavailable, the script retries five more times at 10-minute intervals before stopping.

What does the stated support response time cover?

The provider says its support team typically replies within 12 hours. Its refund policy says support requests are reviewed and answered as soon as possible. The stated reply window concerns response timing; the sources do not describe it as a resolution deadline.

Are the payment terms clear enough to try?

Fits if… the intended use is verification-only and the provider answers your payment and refund questions before registration.

Probably not if… you need a service beyond receiving a verification code or cannot accept the refund exclusions.

Main risk… the refund policy says confirmed payments are final and non-refundable, while the terms describe case-by-case monetary or credit refunds and possible card payments. Resolve the payment method and refund wording with support before registering.

Sources

Below are the public pages behind the facts above, together with the date each one was read.

• getsms.online/terms_conditions.phpchecked 2026-10-31
• getsms.onlinechecked 2026-10-31
• getsms.online/refund_policy.phpchecked 2026-10-31
• getsms.online/api_command_reference.phpchecked 2026-10-31

Notes on the making of this review

Editorial team of Profile Workshop. Profile Workshop compiled this page from the public sources above as they stood on 2026-10-31. We did not test the service ourselves. We revise the text whenever those sources are updated.

Last updated: 2026-10-31

Right of reply

Do you represent GetSMS.ONLINE and see an error or outdated information here? Write to us with evidence. Once the correction is documented, we fix the entry or take it down. Payment never gets an entry removed or softened.

Our contact for replies

No data available

Response time

No data available

Contact · Affiliate disclosure

More write-ups filed under SMS mailing

• Onlinesim — SMS mailing