Faroe Islands Verification Numbers for Developers and QA Teams

Calling code +298OTP Gateway from $0.20 per codeDedicated numbers: US & Canada onlyAPI id: fo
Quick answer

Yes, OTP Route can receive Faroe Islands (+298) verification codes through its OTP Gateway, starting from $0.20 per code, and show them in the dashboard or hand them to your code by API polling or a signed webhook. Each order is a single-use number held open for 20 minutes, and the charge only sticks if an SMS actually comes in.

Should I use a one-off code or a line I keep for the Faroe Islands?

Start with the question that decides everything else: does your account or test case need to receive one code, or does it need the same number again next month?

  • One code, then done — signing up a QA account, checking that a Faroese sign-up screen accepts a +298 number, confirming a localized OTP template renders. The OTP Gateway covers this.
  • The same number for months — a staging login that re-verifies, a shared operations inbox, a support line. That calls for a Dedicated Number, and those are sold self-serve only in the United States and Canada, from $1.95/month.

There is no self-serve long-term Faroese line. If your team truly needs one, write to [email protected]; whether anything can be arranged depends on local rules and is not something we can promise. Our guide to temporary vs dedicated numbers walks through the trade-offs in more depth.

Which services can send codes to a +298 route?

The Faroese route currently lists more than 300 services. Popular ones in the live snapshot include WhatsApp, Telegram, Google (Gmail & YouTube), Facebook, Instagram, TikTok, X (Twitter), ChatGPT (OpenAI), Microsoft & Outlook, Amazon, Discord, LinkedIn, Signal and Airbnb.

Inventory on a small island route moves during the day, so treat that list as a starting point rather than a promise. Before a test run, ask GET /api/v1/countries and GET /api/v1/services what is live right now, or open the country picker in the dashboard. If a service is missing for +298, the Denmark and Iceland routes are the nearest Nordic alternatives for a comparable test.

How does the Faroe Islands OTP API flow work from request to code?

Create a Bearer key in the Developer console; live keys carry the or_live_ prefix and every call goes to https://otproute.com/api/v1. A typical run has four moves:

  1. Price check with GET /api/v1/prices?country=fo&service=telegram. The figure comes back live, so your job can stop early if it looks wrong.
  2. Order with POST /api/v1/activations and a JSON body such as {"service": "telegram", "country": "fo"}. Keep the activation id from the response.
  3. Wait for the code. Either poll GET /api/v1/activations/{id} at a modest interval or subscribe a webhook endpoint to activation.sms_received, activation.expired and activation.cancelled.
  4. Release early with POST /api/v1/activations/{id}/cancel if the test aborts.

Webhook calls are signed with X-OTPRoute-Signature: t=<unix>,v1=<hex>. Your receiver should rebuild the HMAC-SHA256 of <t>.<raw body> with that endpoint's secret, match it against v1 using a constant-time comparison, and ignore any delivery whose timestamp is too old. Accounts allow 10 keys, 5 webhook endpoints and 300 requests per minute; the API reference lists every field.

Can someone without code order a Faroese number?

Yes. Operations and support staff can do the whole thing in a browser:

  1. Sign in and open the OTP Gateway page.
  2. Choose the Faroe Islands, then the service you are verifying.
  3. Confirm the price shown before ordering and click to reserve the number.
  4. Paste the +298 number into the app's sign-up or login screen.
  5. Watch the order card; the code appears there when the SMS lands.

The number belongs to that single activation, so finish the step inside the 20-minute window rather than saving it for later.

What is unusual about storing and validating +298 numbers?

The Faroese plan is closed and short. Subscriber numbers are six digits, there is no trunk prefix to add or strip, and the canonical E.164 form is simply +298 followed by those six digits. That brevity breaks more forms than you might expect: validators written around eight-to-ten-digit national numbers reject a perfectly valid Faroese entry, and some databases pad or truncate short values. Store the full E.164 string, validate with country-aware rules and let your test suite include a six-digit case.

Faroese and Danish are both widely used on the islands, while many global apps still send their codes in English or follow the device locale. If you localize your own messages into Faroese, letters such as ð and á fall outside the GSM-7 default alphabet, so the message switches to UCS-2 and fits fewer characters per segment. Check that on a real route before launch.

Teams usually test here when a Nordic rollout adds the islands, when an app serves local shipping, fishing or tourism businesses, or when a localization pass needs proof that a +298 sign-up really works.

What if my Faroese code never shows up?

A missing code is usually a route or acceptance issue, not a bug in your integration. Work through it calmly:

  • Let the 20-minute window run; some services queue SMS before sending.
  • Check whether the service accepts virtual numbers at all, since some do not and simply never send.
  • Try again later, or try a different service route for the same scenario.
  • Avoid re-ordering in a tight loop; spacing attempts out is kinder to the route and to your wallet history.

A Faroese order that ends empty, or one you cancel yourself, is credited back to the wallet in full without a ticket. Our article on reducing failed OTP deliveries goes further into route choice and retry spacing.

How is a Faroe Islands verification billed?

Faroese orders draw on the same prepaid USD wallet as every other OTP Route purchase, with no subscription tier and no monthly charge. Top up by card or with USDT/USDC stablecoins, and each top-up or number purchase produces a PDF invoice by email. Code prices start at $0.20 per code and vary by service and country; the pricing page and the prices endpoint always show the current figure. For integration work, a development account can be switched to sandbox on request so simulated numbers and codes flow through your handler without touching wallet funds. Use it for your own products and accounts, follow each service's terms, and remember the Acceptable Use Policy applies.

Frequently asked questions

Can I test a +298 sign-up flow without a Faroese SIM card?

Yes. Order a Faroe Islands number on the OTP Gateway, enter it in your sign-up form and read the code from the dashboard or your webhook.

What country id does the API use for the Faroe Islands?

Use fo as the country value in POST /api/v1/activations and in price queries.

How many digits does a Faroese phone number have?

Six, with no trunk prefix. Written in E.164 it is +298 followed by those six digits.

Is there a monthly Faroese number I can keep?

Not as a self-serve product; long-term Dedicated Numbers exist only for the US and Canada. You can email [email protected] to ask, but availability is not assured.

Do I pay when the service never sends the SMS?

No. If no message arrives within 20 minutes, or you cancel first, the amount is returned to your wallet automatically.

Can I try the integration before funding the wallet?

Ask for sandbox mode on a development account. It returns simulated numbers and codes so you can test the full flow end to end.

Why does the list of services for +298 change during the day?

Availability on each route shifts as numbers are used and replenished, which is why the API reports what is live at the moment you ask.

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.

Route your first OTP in minutes

Create a free account, top up your USD wallet and order a number from the dashboard or the API. No monthly fee.