Tinder
Tinder copied to clipboard
fbessez
I think they patched this API
Yeah I can't authenticate with SMS. Any update on this?
I'm getting this with every single phone number I try
{'meta': {'status': 200}, 'data': {'otp_length': 6, 'sms_sent': False}}
I've currently able to get tokens from facebook using config file with email and password. Not sure what your trouble is. I haven't tried via SMS.
Tinder changed the sms login endpoint to v3. The request payload are encoding as gzip
POST https://api.gotinder.com/v3/auth/login?locale=en
Tinder changed the sms login endpoint to v3. The request payload are encoding as gzip
POST https://api.gotinder.com/v3/auth/login?locale=en
Can you help me? How to make this request now? For example in Java or Postman?
I have the same issue. I've tried basically every single number format in existence but it still gives
phone_number= "+447777777777"
phone_number= "+44 07777777777"
phone_number= "4407777777777"
phone_number= "447777777777"
phone_number= "+4407777777777"
NOTHING works. I always get sms sent as false and
print(log_code)=false
Can someone please put an updated version of the code for phone_auth_token.py? you would be a saint! thank you
Who wants to sniff Tinder API of the latest official app (v3 api version), you can write to me and I'll explain how to do it. Email is in my profile.
@RMatushkin I'd be interested in learning how to sniff the new Tinder API. Let me know if you're still available to explain it to me.
The authgateway part of the api should not have changed (see my pull request). However, there's a whole lot of gRPC type stuff that's primed and ready to go in version 11.30.1 although I suspect that 11.29.0 is still is still being maintained right now. It's only a matter of time.
I have all of the protobuf adapters created for Python but there's also the websocket aspect of things. It's only a matter of time before the whole thing is likely to be switched over to a protobuf-based gRPC system.
The auth gateway, btw, should remain the same. It's everything else that is likely to change.
I've had some health issues (COVID long-haulter? Or just opportunistic infection? Either way it's been had to get proper care here) lately but I'd be happy to point anyone interested in creating a fuller, documented, and at least temporarily future-proof api client. It essentially would require work to be done from the ground up at this point.
Anyway, gitee.com/auf/tinder-grpc-exploration
