Checklist: Receiving eBay SMS Codes on an OTP Route Number

When does eBay ask for a phone number?

eBay uses a phone number at several points: it may confirm one during registration, offer text-message codes as a two-step verification method, send a code when a sign-in looks unusual, and ask for a verified number while a seller account is being set up. Those are the moments a marketplace integration, a listing tool or an internal QA suite needs to reproduce. OTP Route has no affiliation with eBay; the name is a trademark of its owner.

Typical requests come from three groups: engineers building listing or order-sync tools who need a working test account, QA teams that must sign off eBay login inside a wider marketplace integration, and operations staff who want account recovery to land on a team-controlled number rather than someone's personal phone. The marketplaces solution page covers that last case.

Pre-flight checklist before you order

• Pick the market first. The number's country should match the eBay site and account you are testing; a UK seller flow wants a UK number.
• Confirm price and availability with GET /api/v1/prices?country=<id>&service=ebay.
• Fund the wallet by card or USDT/USDC; there is no plan to buy.
• Register a webhook endpoint and store its secret, or plan to poll.
• Read eBay's User Agreement and make sure the account belongs to a real person or your business.
• Ask for sandbox mode on a development account if you only need to exercise your own code path.

Which countries carry the eBay route?

The ebay service is listed in 198 countries. Teams usually start with the markets where eBay runs local sites: United States, United Kingdom, Germany, Italy, Australia, France, Spain, Canada, Austria, Ireland, Belgium, Switzerland, the Netherlands, Poland and Hong Kong. Choosing the account's home market keeps the verification consistent with the address, currency and language the account expects.

If you test several eBay sites, keep a small mapping in your test config from site to api_country value, so the number always comes from the same market as the account under test.

Step by step through the API

1. Create a key in the Developer console; it starts with or_live_ and goes in a Bearer header to https://otproute.com/api/v1.
2. Call POST /api/v1/activations with {"service": "ebay", "country": "<id>"}, using the api_country value such as gb or de.
3. Enter the returned number in eBay and request the text.
4. Wait for activation.sms_received on your endpoint, check X-OTPRoute-Signature (HMAC-SHA256 of "<t>.<raw body>"), reject old timestamps, and key processing on the activation id so a retried delivery is harmless.
5. Or poll GET /api/v1/activations/{id}, staying under 300 requests per minute.
6. Call POST /api/v1/activations/{id}/cancel if the test is abandoned.

The CI pipeline guide shows how to wire this into automated runs.

Doing the same from the dashboard

Open the OTP Gateway, search for eBay, select the country, confirm the live price and copy the number. Paste it into eBay, ask for the code, and watch it appear in the activation panel. The 20-minute window and refund rule are identical to the API path.

Non-technical colleagues who only verify an account once or twice a quarter usually prefer this route, while automated suites belong on the API.

Troubleshooting a missing eBay code

• eBay may decline virtual numbers on some flows; the automatic refund covers that case.
• Let the full window run before cancelling.
• Retry later, or on another country route that still matches the account, instead of re-ordering in a tight loop.
• Check that the country picker in eBay's form matches the number's dial code.

The article on reducing failed OTP deliveries has more ideas.

Record the activation id and country with each attempt; patterns become obvious quickly when a particular site or flow keeps declining a route.

When a Dedicated Number fits better

A gateway number serves one code and then goes away, which is wrong for a seller or staging account your team logs into every week. For that, a Dedicated Number in the United States or Canada, from $1.95/month, keeps receiving texts in the dashboard and on number.sms_received, and can be released whenever the account is retired. Compare both on the virtual numbers page. Whatever you choose, OTP Route is for testing and running your own legitimate eBay accounts and products, and its Acceptable Use Policy applies.

Frequently asked questions

Can I receive an eBay OTP without a SIM card?

Yes. Order an OTP Gateway number for the ebay service and the code shows up in the dashboard or arrives through the API.

What service id does eBay use in the OTP Route API?

The service id is ebay, used with a country id in the activation request.

How many countries offer an eBay verification number?

The eBay route is currently listed in 198 countries; check the live list before each run, because availability shifts.

What does eBay SMS verification for testing cost?

From $0.20 per code, with the exact price depending on country and returned by the prices endpoint.

Why did eBay reject my virtual number?

Some eBay flows refuse virtual numbers. You are not charged when no code arrives, so retry later or with a different country route that matches the account.

Which number type suits an eBay seller account we share as a team?

A US or Canada Dedicated Number, because it stays with you and can receive later sign-in codes.

Can I use OTP Route numbers to reopen a suspended eBay account?

No. Follow eBay's terms, keep one account per real person or business, and use the service only for your own legitimate products.

Service names are trademarks of their respective owners. OTP Route is not affiliated with them. Use numbers lawfully, follow each service's terms and our Acceptable Use Policy.