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.

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

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

Request body

usernamestring required

The portal account's e-mail address, or its phone number in +49… form where the platform signs in with one.

login_tokenstring

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_tokenstring

reCAPTCHA token, where the portal's form demands one.

captcha_referencestring

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.

Example request

{
  "username": "name@example.com",
  "login_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9…",
  "captcha_token": "03AGdBq26…",
  "captcha_reference": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9…"
}

Response

Platform-native JSON payload (ScrapeCreators-compatible).

Changes

No recorded changes to this operation across all 1 revision of this API.