1. User Object (e.g., User in Bot API, td_api.user in TDLib, User in MTProto)
This is the fundamental data structure representing a Telegram user or bot. It’s found ubiquitously whenever you get information about who sent a message, who’s in a chat, or who you’re interacting with.
Common Fields:
id (or id_ in TDLib): Unique identifier for this user or bot. This is the primary key for a Telegram user.
first_name: User’s or bot’s first name.
username (optional): User’s or bot’s unique username (e.g., @telegram). This is crucial for privacy as it allows finding and messaging without a phone number.
phone_number (optional): The user’s phone number. Crucially, this field is often null or empty due to privacy settings. It is only populated if the authenticated user (or bot) has permission to see the other user’s number according to their privacy settings, or if the user explicitly shared it (e.g., via a request_contact button for bots). For the current
This structure is specifically used when a user shares their phone number (e.g., via the request_contact keyboard button in the Bot API) or when telegram number database defining a contact to add/edit.
Common Fields:
phone_number: The shared phone number. This field will always be present when a Contact object is explicitly shared by a user.
first_name: Contact’s first name.
last_name (optional): Contact’s last name
user_id (optional): The user’s how often should you update a phone number list Telegram ID, if the phone number belongs to a registered Telegram user.
3. Full User Information (e.g., UserFull in MTProto! td_api.userFull in TDLib)
This provides more comprehensive details book your list about a! specific user, usually retrieved by a dedicated API call for a full profile.