Skip to main content
GET
/
api
/
v1
/
auth
/
me
Get current user profile with full overview
curl --request GET \
  --url https://handauncle-backend-prod-205012263523.asia-south1.run.app/api/v1/auth/me \
  --header 'Authorization: Bearer <token>'
{
  "success": true,
  "data": {
    "user": {
      "id": "<string>",
      "fullName": "<string>",
      "accountStatus": "active",
      "createdAt": "2023-11-07T05:31:56Z",
      "email": "jsmith@example.com",
      "phoneNumber": "<string>",
      "avatarUrl": "<string>",
      "authProvider": "<string>",
      "preferences": {
        "language": "<string>",
        "theme": "<string>",
        "notifications": true
      },
      "deviceId": "<string>",
      "platform": "android",
      "phoneVerified": true,
      "emailVerified": true,
      "last_login_at": "2023-11-07T05:31:56Z"
    },
    "usage": {
      "conversations": {
        "total": 123,
        "active": 123,
        "archived": 123,
        "deleted": 123,
        "lastActiveAt": "2023-11-07T05:31:56Z"
      },
      "shares": {
        "total": 123,
        "active": 123,
        "expired": 123,
        "revoked": 123,
        "totalViews": 123,
        "lastSharedAt": "2023-11-07T05:31:56Z"
      }
    },
    "profileContext": {
      "static": [
        "<string>"
      ],
      "recent": [
        "<string>"
      ],
      "frequent": [
        "<string>"
      ]
    }
  },
  "meta": {
    "timestamp": "2023-11-07T05:31:56Z",
    "requestId": "<string>"
  }
}
Returns the complete user profile overview for the authenticated user. Requires a valid Auth0 access token in the Authorization header.

Response

The endpoint returns a comprehensive profile overview including:
FieldDescription
userFull user object (id, email, name, avatar, preferences, etc.)
usage.conversationsConversation statistics (total, active, archived, deleted, lastActiveAt)
usage.sharesShare statistics (total, active, expired, revoked, totalViews, lastSharedAt)
profileContextCached context cues (static, recent, frequent) used by AI orchestration

Example Response

{
  "success": true,
  "data": {
    "user": {
      "id": "683b7e9f465b1b4e6753627a4f",
      "email": "investor@example.com",
      "fullName": "Puneet",
      "avatarUrl": "https://cdn.auth0.com/...",
      "emailVerified": true,
      "preferences": {
        "language": "en",
        "theme": "dark"
      },
      "createdAt": "2025-12-01T07:00:00.000Z",
      "updatedAt": "2025-12-04T10:00:00.000Z"
    },
    "usage": {
      "conversations": {
        "total": 42,
        "active": 38,
        "archived": 3,
        "deleted": 1,
        "lastActiveAt": "2025-12-04T09:30:00.000Z"
      },
      "shares": {
        "total": 5,
        "active": 4,
        "expired": 0,
        "revoked": 1,
        "totalViews": 127,
        "lastSharedAt": "2025-12-03T15:00:00.000Z"
      }
    },
    "profileContext": {
      "static": ["Financial goals: Retirement planning"],
      "recent": ["Discussed SIP investments"],
      "frequent": ["Portfolio review", "Tax planning"]
    }
  }
}

Auto-sync Behavior

If the user does not exist locally or is missing critical data (name/email), the controller:
  1. Fetches user info from Auth0’s /userinfo endpoint
  2. Creates or updates the local MongoDB record
  3. Returns the complete profile overview
This ensures users are always synced on their first authenticated API call.

Authorizations

Authorization
string
header
required

Auth0 access token for registered users.

Response

Profile overview returned

success
enum<boolean>
required
Available options:
true
data
object
required
meta
object
required