Service selection

SMS verification for OpenAI, Google and Telegram

RaySMS provides a service-and-country catalog for receiving SMS verification codes. Identify your account workflow, inspect the matching service and compare current quotes. This guide explains the three entries and what to check before a paid order.

Open the matching service catalog

The current identifiers are OpenAI: dr; Google,youtube,Gmail: go; and Telegram: tg. The buttons below open the marketplace with that service selected. Choose a country there to inspect the available offers and USD price. Other Google products can have separate entries, so read the service name rather than treating every Google-related entry as interchangeable.

Country IDs are catalog identifiers, not telephone dialing prefixes. A displayed quantity is reported availability, not a count of successful deliveries. Quotes can change and viewing one does not reserve a number.

OpenAI: check the ChatGPT or Codex verification step

For OpenAI-related number quotes, start with OpenAI (dr). OpenAI generally does not require a phone check for account creation or ChatGPT, but may require one for Codex in ChatGPT desktop. Initial API-key creation requires it. Follow your account's prompt.

OpenAI accepts mobile numbers, excluding landlines, VoIP, Google Voice and premium numbers. SMS and, in selected regions, WhatsApp are supported. Check the actual number type before ordering.

The RaySMS operator reports successful OpenAI verification in personal day-to-day use. This is individual experience, not a measured success rate or evidence that every ChatGPT or Codex flow will work.

Google can limit a number or choose another verification step

Google may require phone verification at signup or login, limit a number's account creation and verification uses, or reject it. Follow the options and waiting time on Google's screen before creating a RaySMS order.

For account recovery, Google recommends a mobile number that belongs only to you and that you use regularly. Short-term SMS reception does not provide continuing control of a recovery number.

Telegram does not always send the code by SMS

Telegram requires a mobile number in international format; landlines are unsupported. A login code may arrive in an existing Telegram session instead of SMS. Keep control of the linked number for future access.

The RaySMS order view displays SMS received for that order, not your Telegram chat history. Compare the platform's delivery prompt with the order status when checking where a code went.

Before ordering, and when a code does not arrive

Use the service only for accounts and workflows you are authorized to manage. Keep the same RaySMS order open while checking its outcome, especially if a request times out.

  • Confirm the service, country, current price and available wallet balance before purchase.
  • After purchase, enter the full international number in the target platform, request its SMS code and return to the RaySMS order to read the received message.
  • If no SMS arrives, inspect the order status and expiry, and respect the target platform's resend timer.
  • Cancel only when the order permits it; a refund requires the corresponding confirmed outcome, not just a countdown reaching zero.
  • For an unclear result, give support the order ID and error context, with verification codes and API keys removed.

Inspect the API without making a purchase

The public Python walkthrough reads services, countries and price offers with GET requests. It needs no API key, login or funded wallet, and contains no order or payment call. Prices use integer millionths of a US dollar, which the example converts with Decimal.

Use it to understand the response fields before adding authenticated operations. The developer guide covers the separate order workflow, including a price limit and idempotency. RaySMS brings received verification messages and their order status into the same workflow.

Browse services and current quotes →