Skip to end of metadata
Go to start of metadata

Get user's profile in the format requested using units in the unit system which corresponds to the Accept-Language header provided.

Access Type: Read

Rate Limited: Yes

OAuth: oauth_token is optional, if omitted you should explicitly specify <user-id>.

Privacy: Basic profile is always public, About Me (Friends or Anyone), Age and height (Friends or Anyone), Location (Friends or Anyone), My Body (Friends or Anyone) privacy permissions grant granular access to other user's respective profile fields, considering:

  • authenticated owner will receive all values, others will receive the correct values for accessible fields and empty values otherwise:
    empty string, "NA" (empty gender), 0 (empty height), default avatar etc., some values revealed to authorized user only,
  • About Me controls aboutMe, gender, avatar,
  • Age and height controls dateOfBirth, height,
  • Location controls country, city, state, timezone, offsetFromUTCMillis,
  • My Body controls weight.

Resource URL

GET /<api-version>/user/<user-id>/profile.<response-format>


The API version. Currently 1.


User's encoded id or "-" (dash) to indicate user currently authenticated via the token credentials provided.


The response format. Currently supported response formats are json and xml for responses in JSON and XML, respectively.



Via token credentials. oauth_token authentication header parameter is optional.

Request Headers



The measurement unit system to use for response values.


API Response in format requested: JSON or XML.

Response body format

Note: Text within <> is a descriptive place holder for a value or repeated elements.

JSON Response

Note: Text within [] is a descriptive place holder for a value or repeated elements.

XML Response

1. Note that <displayName> field is present at all times. It contains one of the following – <nickname>, first name with the leading letter of last name, or part of user's email address before "@" (in case nickname and fullName empty).
2. Units (<glucoseUnit> etc.) represent the user's default unit settings in the web UI. Note that <heightUnit> is also used as a default for all other body measurements (i.e. neck, bicep etc.).
3. <locale> reveals the local website version that user is currently using (en_US, en_GB...) 



JSON Response
XML Response


  • No labels