A big thank you to @rtt for their initial compilation of the Tinder API documentation. This document is meant to offer an updated guide for interacting with the Tinder API as of June 2018.

Please note that this documentation may become outdated over time; always refer to the latest API specifications when developing applications.

The following table summarizes the host and protocol details for the Tinder API.

When making API calls, it's essential to include appropriate headers. Here are the headers that you'll need:

All endpoints should be appended to the host URL, https://api.gotinder.com. Make sure to include the required headers with your requests. The only exception is the /auth endpoint, which should not be provided with the X-Auth-Token header.

The table below lists various endpoints with their purposes, expected data, and the HTTP method to use.

(For the full list of endpoints, please refer to the attached table in the original documentation.)

Tinder API uses standard HTTP status codes to indicate the success or failure of an API request:

To authenticate using your Facebook account, include your Facebook username and password in the config file. The fb_auth_token.py module will programmatically retrieve your facebook_access_token and fb_user_id, which are then used to generate a tinder_auth_token via tinder_api.py, granting you access to your Tinder data. Happy swiping! 🎉

SMS authentication is straightforward. Run phone_auth_token.py and input your phone number when prompted. Enter the code you receive via SMS to retrieve your token. Keep in mind that there is a rate limit for the number of SMS you can receive in an hour. It's advised to use your token within its lifetime (24 hours) instead of requesting a new one each time.

To proceed, add your token to tinder_config_ex.py as the value for tinder_token. You're now prepared to start using the API!

This feature creates a local dictionary for each of your matches containing keys like message count, age, name, photos, and more. For example:

{
  '123456': {
    // Detailed info about the match would go here.
  },
  // More matches would follow.
}

Sort your matches by attributes such as "age", "message_count", and "gender". Here's a sample structure:

[
  // Tuple with match ID and corresponding match info.
]

The friends_pingtimes() function used to return the time since each Facebook friend last used Tinder. However, Tinder's change to a constant ping_time has made this feature obsolete.

This feature used to allow you to access profile information and ID of your Facebook friends on Tinder. With the ID, you could call api.get_person(id) to get more detailed information. This feature is no longer available.

We welcome contributions from the community! Whether you're fixing bugs, adding new features, or improving documentation, your input is invaluable. Take a look at our Contributing Guide to get started. Also, we'd love to hear about your experience with Ultralytics products. Please consider filling out our Survey. A huge 🙏 and thank you to all of our contributors!

Ultralytics is excited to offer two different licensing options to meet your needs:

• AGPL-3.0 License: Perfect for students and hobbyists, this OSI-approved open-source license encourages collaborative learning and knowledge sharing. Please refer to the LICENSE file for detailed terms.
• Enterprise License: Ideal for commercial use, this license allows for the integration of Ultralytics software and AI models into commercial products without the open-source requirements of AGPL-3.0. For use cases that involve commercial applications, please contact us via Ultralytics Licensing.

For bug reports, feature requests, and contributions, head to GitHub Issues. For questions and discussions about this project and other Ultralytics endeavors, join us on Discord!