---
title: "NOT AVAILABLE: Bumble retired the API these routes speak. Its endpoint answers every call, the anonymous handshake included, with 'Session not found (0030-3001-0051)', and the Bumble app does not use that endpoint at all: it speaks a binary protocol over a TLS socket to bma.bumble.com:443. No credentials get through until that transport is built, so these calls answer 502 instead of pretending to sign in. Ask Bumble to send the one-time login code. This platform has no password at all, so this is where a sign-in starts: it answers with a `login_token` that the login route takes back together with the code. Nothing is stored yet."
method: POST
path: "/v1/bumble/challenge"
tags: ["Bumble"]
---

# NOT AVAILABLE: Bumble retired the API these routes speak. Its endpoint answers every call, the anonymous handshake included, with 'Session not found (0030-3001-0051)', and the Bumble app does not use that endpoint at all: it speaks a binary protocol over a TLS socket to bma.bumble.com:443. No credentials get through until that transport is built, so these calls answer 502 instead of pretending to sign in. Ask Bumble to send the one-time login code. This platform has no password at all, so this is where a sign-in starts: it answers with a \`login_token\` that the login route takes back together with the code. Nothing is stored yet.

`POST /v1/bumble/challenge`

## Request

- Base URL: `https://api.scraper-api.com`
- URL: `https://api.scraper-api.com/v1/bumble/challenge`
- Auth: API key in header `x-api-key`

**Live endpoint.** Credit cost: **1** (1 request = 1 credit).

## Request body

- object
  - `username` string, required: The portal account's e-mail address, or its phone number in +49… form where the platform signs in with one.
  - `login_token` string: The token the challenge route handed back, which binds the code to the attempt it was sent for. On a portal that only asks for a code when it does not recognise the sign-in, this carries that mailed code itself.
  - `captcha_token` string: reCAPTCHA token, where the portal's form demands one.
  - `captcha_reference` string: The reference the portal issued together with that bot check. Tinder verifies the solved token against it, so a token without it is never checked.

## Response `200`

Platform-native JSON payload (ScrapeCreators-compatible).

## Other responses

- `400`: Missing or invalid parameters.
- `401`: Missing or invalid API key.
- `402`: Not enough credits.
- `429`: Rate limit exceeded.
- `502`: Upstream scrape failed.

---

[API](https://skmtc.dev/scraper-api/apis/scraper-api-com-api.md) · [All operations](https://skmtc.dev/scraper-api/apis/scraper-api-com-api/llms.txt) · [OpenAPI document](https://skmtc.dev/scraper-api/apis/scraper-api-com-api/revisions/3c0343a0e65a?raw)