Both user profile endpoints operate on the account of the currently logged-in user, identified by the Firebase token in the request. Neither endpoint accepts a user ID parameter — the identity is always derived from the auth token.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/AndrewwCO/Panahashi/llms.txt
Use this file to discover all available pages before exploring further.
GET /users/me — fetchMyProfile()
Returns the profile record for the authenticated user.
Response fields
The user’s display name.
The user’s phone number.
The user’s email address as registered in Firebase Auth.
Firebase Cloud Messaging token used to send push notifications to this user’s device.
Example
PATCH /users/me — updateMyProfile(displayName, phone, fcmToken)
Updates one or more fields on the authenticated user’s profile. Only the fields you provide are changed; omitting a parameter leaves that field unchanged.
Request parameters
New display name for the user. Omit to leave unchanged.
New phone number for the user. Omit to leave unchanged.
Updated Firebase Cloud Messaging token. Pass this whenever the device token rotates to keep push notifications working. Omit to leave unchanged.
How the request body is built
Only defined arguments are included in the PATCH body, matching the implementation inservices/api.js:
Response fields
Returns the updated user profile object with the same shape asfetchMyProfile().