Getting Spanish +34 verification codes into your tests and dashboards

Do you need a +34 number for one code or a Spanish line you keep?

Start here, because it decides which product you open. Almost every Spanish task we see is single-use: confirming that a new sign-up screen sends its code, re-running an onboarding regression after a release, or verifying a business profile for a team that operates in Spain. That is OTP Gateway territory, where each number exists to catch exactly one code.

If the plan is to log back in to the same account months from now, a one-time number is the wrong tool, and a Spanish replacement is not on the shelf. Self-serve Dedicated Numbers cover only the United States and Canada, from $1.95/month, with inbound SMS, outbound SMS and browser calling. There is no self-serve long-term line for Spain; you can email [email protected] to ask, but local rules decide whether anything is possible.

For a recurring staging login that does not need a Spanish identity, a US or Canadian line on the virtual numbers page is usually the cleaner answer.

What is specific about Spanish phone numbers?

Spain uses no trunk prefix. A national number is nine digits, dialed the same way at home as it is written after +34, and mobiles begin with 6 or 7. In E.164 a Spanish mobile is therefore +34 followed by nine digits starting with 6 or 7, and normalization mostly means stripping spaces, dots and an optional 0034 international prefix that some users paste in.

Two checks are worth adding to your form tests: a number entered with the 0034 prefix should collapse to the same stored value as one entered with +34, and a landline starting with 9 should be flagged early if your flow needs a mobile.

Language matters too. Spanish is the national language, while Catalan, Galician and Basque are co-official in their regions, so a Spanish user may run an app in any of the four. Most verification texts reach +34 numbers in Spanish or English, but your extraction should never depend on surrounding words.

Which services work with a Spain verification number today?

The Spanish route covers more than 1,900 services. Frequently requested ones include WhatsApp, Telegram, Google (Gmail & YouTube), Instagram, Facebook, TikTok, Amazon, Airbnb, eBay, Microsoft & Outlook, LinkedIn, Signal, Claude and Netflix.

Availability is a live value, not a fixed list. Query GET /api/v1/countries and the prices endpoint for es at the start of each run so a temporarily missing service is skipped cleanly.

How do non-developers order a Spanish number in the dashboard?

Product managers, support leads and localization reviewers rarely want to touch an API key, and they do not have to.

1. Sign in and open the OTP Gateway.
2. Pick Spain, then the service whose screen you are checking.
3. Read the price displayed before you confirm; it varies by service.
4. Copy the +34 number into the app and request the code.
5. Keep the tab open; the message text appears in the activation row once it lands.

This is how many teams handle the occasional manual check on a Spanish-language build, or a one-off confirmation for a business account run by the operations desk.

How do I wire the Spain OTP API into CI?

Automated suites call the same REST endpoints under https://otproute.com/api/v1 with a Bearer key prefixed or_live_. Spain's country id is es.

• GET /api/v1/prices?country=es&service=<id> returns today's cost for the pairing.
• POST /api/v1/activations with {"service": "instagram", "country": "es"} creates the order and hands back a number plus activation id.
• GET /api/v1/activations/{id} reports status for polling; POST /api/v1/activations/{id}/cancel releases an order your test no longer needs.
• GET /api/v1/balance lets the pipeline stop early when funds are low.

For parallel jobs, subscribe a webhook endpoint to activation.sms_received, activation.expired and activation.cancelled. Confirm the X-OTPRoute-Signature header by recomputing HMAC-SHA256 over <t>.<raw body> with your endpoint secret, reject old timestamps, and store results by activation id so retries stay harmless. Our walkthrough of webhook-based OTP capture shows a full handler. Limits are 10 keys, 5 endpoints and 300 requests per minute per account.

Why might a Spanish code fail to arrive, and what then?

Each activation is open for 20 minutes, and you pay only when a code arrives. A cancelled order, or one whose window expires without an SMS, is refunded to the wallet in full and without a ticket.

When a +34 order stays empty, give it the full window first. If it still fails, the most common cause is that the service declines virtual numbers for that flow, which the refund rule is designed to absorb. After that, try again at a different time or with another service route, and add a pause between attempts so an automated job does not hammer the endpoint. Our mobile app verification page discusses how to design tests that tolerate this.

How is OTP Route billed for teams working in Spain?

There is a single prepaid wallet in US dollars, charged per use, without subscriptions or tiers. Teams top up with a card or with USDT/USDC, and a PDF invoice is emailed for every top-up and number purchase, which keeps EU bookkeeping straightforward. Current rates sit on the pricing page.

During integration, request a sandbox switch on your development account; it returns simulated numbers and codes so the Spain path can be tested end to end at no cost. OTP Route is meant for testing and operating your own legitimate products and accounts: follow each service's terms, and remember that the Acceptable Use Policy covers every order.

Frequently asked questions

Can I check my app's Spanish sign-up flow without a Spanish SIM?

Yes. Order a +34 number from the OTP Gateway, enter it in the app and the code appears in the dashboard or through the API.

What is the API country id for Spain?

It is es, used in calls like POST /api/v1/activations and GET /api/v1/prices.

Do Spanish numbers have a trunk zero I need to remove?

No. Spain has no trunk prefix, so the nine national digits follow +34 directly; just strip spaces and any 0034 prefix.

What does a +34 number for testing cost?

From $0.20 per code. The live price per service comes back from the API and is shown in the dashboard, and you pay only if the code arrives.

Can I rent a Spanish number for long-term logins?

No self-serve option exists for Spain. Long-term Dedicated Numbers are US and Canada only, from $1.95/month; email [email protected] to ask about Spain.

Will codes come in Catalan or Basque?

Occasionally an app sends in the user's chosen language, but Spanish or English is most common. Extract the digits so wording never breaks your test.

Is there a way to test without spending wallet funds?

Yes. Ask for sandbox on your development account to receive simulated numbers and codes.

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.