> ## Documentation Index > Fetch the complete documentation index at: https://api.fanvue.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Get current user > Get details of the currently authenticated user. **Required scope** * `read:self` — Access your own user profile information, including basic account details and settings. ## OpenAPI ````yaml /openapi.json get /users/me openapi: 3.1.0 info: title: Fanvue API version: '0.1' servers: [] security: [] paths: /users/me: get: summary: Get current user description: Get details of the currently authenticated user. operationId: getCurrentUser parameters: - $ref: '#/components/parameters/ApiVersionHeader' responses: '200': description: Current user details content: application/json: schema: type: object properties: uuid: type: string format: uuid email: type: string format: email handle: type: string bio: type: string displayName: type: string isCreator: type: boolean roles: type: array items: type: string enum: - creator - agency - agency_admin description: >- Full non-exclusive set of roles held by the account. Unlike `isCreator`, this expresses that an account can be several things at once (e.g. a creator who also manages an agency). `isCreator` is retained and always equals `roles.includes("creator")`. isDiscoverable: type: boolean description: >- Whether the profile is eligible to appear in Discovery. Reflects the creator's discoverability setting; it is turned off when the account is restricted or fails moderation. Final placement in Discovery and Suggestions feeds also depends on ranking and per-viewer filters, so being discoverable does not guarantee appearance for every viewer. Always false for non-creators. isInCuratedSection: type: boolean description: >- Whether the creator is currently surfaced in Discovery/Suggestions via the manager-controlled recommendation flag. Unlike `isDiscoverable` (which is only eligibility), this reflects active curation and is the signal that a model is being surfaced. Final placement for any given viewer still depends on ranking and per-viewer filters (e.g. already-following, country), so this does not guarantee appearance for every viewer. Always false for non-creators. createdAt: type: string format: date-time updatedAt: type: - string - 'null' format: date-time avatarUrl: type: - string - 'null' bannerUrl: type: - string - 'null' likesCount: type: number fanCounts: type: object properties: followersCount: type: number subscribersCount: type: number required: - followersCount - subscribersCount contentCounts: type: object properties: imageCount: type: number videoCount: type: number audioCount: type: number postCount: type: number payToViewPostCount: type: number required: - imageCount - videoCount - audioCount - postCount - payToViewPostCount required: - uuid - email - handle - bio - displayName - isCreator - roles - isDiscoverable - isInCuratedSection - createdAt - updatedAt - avatarUrl - bannerUrl example: uuid: 3bbe6394-2830-4646-a8ba-4a0a05426947 email: johnny@fanvue.com handle: johnny-doey bio: Content creator and influencer displayName: Johnny Doey isCreator: true roles: - creator isDiscoverable: true isInCuratedSection: false createdAt: '2023-01-15T10:30:00.000Z' updatedAt: '2024-12-01T14:20:00.000Z' avatarUrl: https://media.fanvue.com/user-avatar.jpg bannerUrl: https://media.fanvue.com/user-banner.jpg likesCount: 1250 fanCounts: followersCount: 3420 subscribersCount: 890 contentCounts: imageCount: 145 videoCount: 67 audioCount: 12 postCount: 234 payToViewPostCount: 45 '400': $ref: '#/components/responses/UnsupportedVersionResponse' '401': $ref: '#/components/responses/UnauthorizedResponse' '403': $ref: '#/components/responses/UnauthorizedResponse' '410': $ref: '#/components/responses/SunsetVersionResponse' '429': $ref: '#/components/responses/RateLimitResponse' security: - BearerAuth: - read:self components: parameters: ApiVersionHeader: name: X-Fanvue-API-Version in: header required: true schema: type: string default: '2025-06-26' example: '2025-06-26' description: API version to use for the request responses: UnsupportedVersionResponse: description: API version not supported content: application/json: schema: type: object properties: error: type: string message: type: string required: - error - message UnauthorizedResponse: description: Unauthorized Response content: application/json: schema: type: object properties: error: type: string required: - error SunsetVersionResponse: description: API version no longer supported (sunset) content: application/json: schema: type: object properties: error: type: string message: type: string nextVersion: type: string required: - error - message RateLimitResponse: description: Too many requests - rate limit exceeded headers: Retry-After: description: Number of seconds to wait before retrying the request schema: type: integer X-RateLimit-Limit: description: The maximum number of requests allowed in the current window schema: type: integer X-RateLimit-Remaining: description: The number of requests remaining in the current window schema: type: integer X-RateLimit-Reset: description: The Unix timestamp (seconds) when the rate limit window resets schema: type: integer content: application/json: schema: type: object properties: error: type: string required: - error securitySchemes: BearerAuth: type: oauth2 description: >- OAuth 2.0 access token, presented as a JWT bearer token in the `Authorization` header. Obtain a token via the authorization-code flow; the scopes granted to the token determine which operations it may call. flows: authorizationCode: authorizationUrl: https://auth.fanvue.com/oauth2/auth tokenUrl: https://auth.fanvue.com/oauth2/token refreshUrl: https://auth.fanvue.com/oauth2/token scopes: read:self: >- Access your own user profile information, including basic account details and settings. read:chat: >- Read chat conversations, messages, and chat-related data. This includes viewing chat lists and message history. write:chat: >- Create new chats and send messages. This scope is required for any chat-related actions that modify data. read:experience: >- Exchange a fan's experience token for the resolved experience and the fan's identity, so an embedded fan-facing experience can render the right content. write:experience: >- Request that the creator publish or unpublish a fan-facing experience. The app mints a request token; the creator confirms and Fanvue performs the change. read:fan: Access fan-related data and information within the platform. read:post: Read posts, including post details, comments, likes, and tips. write:post: Create, edit, and manage posts and content on behalf of users. read:media: Access media files, images, videos, and other content assets. write:media: >- Upload, modify, and manage media files and content assets. Also required for vault folder management. read:creator: >- Access creator profiles, content, and creator-specific information. write:creator: Modify creator profiles, settings, and creator-specific data. read:insights: >- Access analytics, metrics, and insights data for performance tracking. read:tracking_links: >- Read tracking links and the users associated with them, including per-user tracking metadata. write:tracking_links: Create and delete tracking links. read:agency: Read agency information, including the agency's team members. write:agency: >- Manage agency team members and invites, including inviting new team members and creators. ````