Tinder

Ask Tinder 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. A PHONE number always hits an Arkose bot check first: Tinder answers this route with 400 and hands out `captcha_public_key`, `captcha_reference` and `data_blob`. Solve it in a browser against that key and blob, then call this route again with `captcha_token` and `captcha_reference`. An E-MAIL address is not gated that way and goes straight through — but it only signs in an account that already carries the address.

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

post/v1/tinder/challenge

Request

  • Base URL: https://api.scraper-api.com
  • URL: https://api.scraper-api.com/v1/tinder/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.