Capturing Bumble SMS codes programmatically

How does the API hand you a Bumble code?

The OTP Gateway treats Bumble as service id bumble. Calls go to https://otproute.com/api/v1 with a Bearer key prefixed or_live_.

1. Choose a market: GET /api/v1/countries lists ids such as gb or de.
2. Price it: GET /api/v1/prices?country=<id>&service=bumble.
3. Order: POST /api/v1/activations with {"service": "bumble", "country": "<id>"}. You receive an activation id and the phone number to type into the app.
4. Collect the code (next section), or call POST /api/v1/activations/{id}/cancel to abandon the run.

A test harness for a dating app typically wraps this in a fixture that returns a fresh number per test case and tears it down afterwards. Endpoint details live in the docs.

Webhook or polling for Bumble OTPs?

Polling GET /api/v1/activations/{id} is the shortest path for a local script. For a device farm or a CI matrix, register a webhook endpoint and listen for activation.sms_received, activation.expired and activation.cancelled.

Two habits keep the receiver trustworthy:

• Verify the signature. The header X-OTPRoute-Signature: t=<unix>,v1=<hex> is an HMAC-SHA256 of <t>.<raw body> keyed with your endpoint secret. Compare in constant time and reject old timestamps.
• Be idempotent. Store results keyed on the activation id so a redelivered event changes nothing.

An account allows 10 API keys, 5 webhook endpoints and 300 requests per minute, which is plenty for parallel test suites.

Where does Bumble ask for a phone number?

Bumble offers phone-number sign-up, sending a one-time code by SMS to confirm the number belongs to the person registering. A code can also appear when logging in on a new device or reinstalling the app, and the verified number can help with getting back into an account later. Exact prompts change as the app evolves, so let your tests assert on the screen you actually see rather than a fixed script.

For a team integrating a dating or social product, those moments matter: the country picker, the number input mask, the code-entry screen and the resend timer all deserve coverage. See mobile app verification for patterns.

Which countries can a Bumble test number come from?

The bumble service is currently listed in 202 countries, including the United States, the United Kingdom, India, Australia, Brazil, Germany, Canada, Mexico, France, Ireland, Spain, the Netherlands, Nigeria and South Africa.

Choose the origin country to mirror whichever scenario the test is meant to reproduce. A UK build, a Brazilian Portuguese locale or an Indian onboarding funnel each expects a phone number from that market, and the app may vary content, language or verification steps by region. Live availability shifts during the day, so query it at run time.

Running the same check from the dashboard

Product managers and support staff can skip the API entirely:

1. Open the OTP Gateway and search for Bumble.
2. Select a country and confirm the price shown.
3. Paste the number into the Bumble sign-up or login screen.
4. Watch the code appear in the dashboard within the 20-minute window.

If you cancel or nothing arrives in time, the amount goes straight back to the wallet. The wallet is prepaid in USD, topped up by card or USDT/USDC, with no monthly fee and a PDF invoice per top-up.

Why might a Bumble code fail to arrive?

Bumble may refuse virtual numbers, or a particular route may be quiet at a given moment. Neither costs you anything, because an activation with no SMS is refunded. Practical steps:

• Wait out the window before deciding it failed.
• Retry later or with a different country route rather than re-ordering immediately in a loop.
• Check your webhook logs for rejected signatures.
• Ask for a sandbox account while building the integration; it returns simulated numbers and codes so you can test the plumbing without spending.

When is a Dedicated Number a better fit than a Bumble OTP?

A one-time number suits a test that ends after sign-up. If a QA account must log in again next week, a number you keep is more practical: Dedicated Numbers in the US and Canada start from $1.95/month, receive inbound SMS in the dashboard and on number.sms_received, and can be released any time. Details are on the virtual numbers page.

Whatever you choose, follow Bumble's terms: one account per real person or business, no duplicate profiles. OTP Route is for testing and operating your own legitimate products and accounts, and the Acceptable Use Policy applies. Bumble is a trademark of its owner, and OTP Route is not affiliated with it.

Frequently asked questions

What is the service id for Bumble in the OTP Route API?

It is bumble, passed in the service field of POST /api/v1/activations.

Can I use a virtual number for Bumble?

You can try, but Bumble may decline virtual numbers. If no code arrives, the charge returns to your wallet.

How long do I have to receive a Bumble OTP?

Each activation is open for 20 minutes and covers one code.

Can I automate Bumble SMS verification for testing in CI?

Yes. Create activations from your pipeline and receive codes on a signed webhook, or use the sandbox while wiring it up.

Which country should I choose for a Bumble phone number?

Match the market your build or test account targets, such as the UK, India or Brazil, and check live availability first.

Is a Bumble number reusable for later logins?

Gateway numbers are single-use. For repeat logins, a US or Canada Dedicated Number you keep is the better choice.

Can I create several Bumble profiles with these numbers?

No. Follow Bumble's terms and the OTP Route Acceptable Use Policy; numbers are for testing and running your own legitimate accounts.

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.