Profile and account

Reading your own profile 🟢

GET /v2/profile?locale=en&include=user,account,likes,boost,super_likes

The include parameter decides which sections the response contains. Without it the response is very thin. Known scopes:

Tip: Only request the scopes you need. The response is smaller and you avoid processing data you don't use. user,likes,boost covers most cases.

Updating your profile and discovery settings 🟢

Updates are split across two endpoints with two different body shapes:

Example: basic discovery settings

{
  "user": {
    "age_filter_min": 25,
    "age_filter_max": 35,
    "distance_filter": 30,
    "gender_filter": 1,
    "bio": "Coffee, code and long walks.",
    "discoverable": true
  }
}

💳 Premium limit: Preference updates (especially preference_filters) return 403 on a free account. Treat that 403 as "not allowed" and don't retry.

Legacy /profile options 🔴

In 2018-era material, POST /profile could also do the following:

These are probably managed today under the plus_control scope via /v2/profile. This has not been confirmed in any current client.

Other profile endpoints

⚠️ DELETE /v2/profile: This request deletes the account. Don't define this route in your client at all, or put it behind an explicit confirmation step. Deleting and re-creating an account repeatedly is reported to get the phone number permanently banned.

Another user's profile 🟡

GET /user/{user_id}?locale=en

The response is a results object similar to a recommendation card: name, age, photos, bio, distance. This data belongs to someone else. Only use it to display what you could already see in the app. Don't store or collect it (see chapter 13).