Tinder

Open a Tinder session with the account's own credentials. Returns an opaque session id to carry in the x-session-id header on the session routes. The portal's own session is the only thing kept, sealed at rest; the password is not stored and cannot be read back out of the session. Tinder has no password: call POST /v1/tinder/challenge first, then send the phone number (or e-mail) as `username`, the code that arrived as `password`, and the challenge's `login_token` alongside them.

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

post/v1/tinder/login

Request

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

passwordstring required

The portal account's password, or the one-time code where the platform has no password.

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.

Example request

{
  "username": "name@example.com",
  "password": "•••••••••",
  "login_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9…"
}

Response

Platform-native JSON payload (ScrapeCreators-compatible).

Changes

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