> ## Documentation Index > Fetch the complete documentation index at: https://help.kajabi.com/llms.txt > Use this file to discover all available pages before exploring further. ## Submitting Feedback If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback: POST https://help.kajabi.com/feedback ```json { "path": "/api-reference/me/my-user-profile", "feedback": "Description of the issue" } ``` Only submit feedback when you have something specific and actionable to report. # My user profile > Returns the current user's profile data. ## Response attributes The response will include the following attributes: * `initials` - A derived attribute that represents the user's initials based on their name. This is typically used for avatar placeholders or compact user displays. For example, "John Doe" would have initials "JD". * `name` - The user's full name. This is a required field that can be: * Set directly as a full name * Automatically generated from first name and last name fields when either changes * Used for display purposes throughout the platform * `email` - The user's email address. This is a critical field that: * Is required and must be unique * Is used for authentication * Can trigger email change notifications * Is used for password recovery * Can be marked as bounced (and reset when email changes) * Is validated against email format requirements * `role_level` - Represents the user's permission level in the system. This attribute: * Common values include: * OWNER - Account owner with full permissions * ADMINISTRATOR - Admin with site management permissions * Determines what actions and resources the user can access * Is used for permission checks throughout the system ## OpenAPI ````yaml /openapi.yaml get /v1/me openapi: 3.1.1 info: title: Kajabi API V1 version: 1.0.1 description: > ## Public API * Server URL `https://api.kajabi.com` * Endpoint paths are prefixed with `/v1` * Version endpoint `GET https://api.kajabi.com/v1/version` * See the [Developers Site](https://developers.kajabi.com) for documentation and examples. * Try the demo [Postman collection](https://www.postman.com/kajabi-apis/beta-public-api-demo/collection/fg4iyaz/kajabi-public-api-v1) ## API Keys * Your API `client_id` and `client_secret` are available on the [User API Keys](https://app.kajabi.com/admin/settings/security) section of the Kajabi Admin Portal. * Custom API Keys can be created with specific permissions. * Click the "Create User API Key" button, enter a name (e.g. "My project"), select the user and permissions, and click "Create". * For security purposes, you may "Delete" or "Rotate" the api credentials at any time; which will invalidate any access tokens granted with the credentials. ## Video Walkthroughs * [Capabilities](https://drive.google.com/file/d/1Puc9B2sSdA-RQb7YMxmUXg4FVoEXytoc/view?usp=sharing) * [Getting Started](https://drive.google.com/file/d/1hbGRShkxven_QMWvgYrerHKURbcZrnvJ/view?usp=sharing) * [Error Examples](https://drive.google.com/file/d/1i0wQK71I1jpaZVsxYwsn62gVj40S_E7Y/view?usp=sharing) * [External Contact Form](https://drive.google.com/file/d/1HqpULXvan5TOK3LvM7nILCuCkCaX0kFT/view?usp=sharing) contact: email: support@kajabi.com name: Support url: >- https://help.kajabi.com/hc/en-us/articles/4404549690523-How-to-Get-Help-From-Kajabi-Live-Agents license: name: Apache 2.0 url: http://www.apache.org/licenses/LICENSE-2.0.html servers: - url: https://api.kajabi.com description: Production security: [] paths: /v1/me: get: tags: - Me summary: My user profile description: > Returns the current user's profile data. ## Response attributes The response will include the following attributes: * `initials` - A derived attribute that represents the user's initials based on their name. This is typically used for avatar placeholders or compact user displays. For example, "John Doe" would have initials "JD". * `name` - The user's full name. This is a required field that can be: * Set directly as a full name * Automatically generated from first name and last name fields when either changes * Used for display purposes throughout the platform * `email` - The user's email address. This is a critical field that: * Is required and must be unique * Is used for authentication * Can trigger email change notifications * Is used for password recovery * Can be marked as bounced (and reset when email changes) * Is validated against email format requirements * `role_level` - Represents the user's permission level in the system. This attribute: * Common values include: * OWNER - Account owner with full permissions * ADMINISTRATOR - Admin with site management permissions * Determines what actions and resources the user can access * Is used for permission checks throughout the system responses: '200': description: Success content: application/vnd.api+json: schema: $ref: '#/components/schemas/me_response' '401': description: Unauthorized content: application/vnd.api+json: schema: $ref: '#/components/schemas/errors_unauthorized' '403': description: Forbidden, insufficient permission to access the resource content: application/vnd.api+json: schema: $ref: '#/components/schemas/errors_forbidden' security: - Bearer: [] components: schemas: me_response: type: object properties: data: type: object properties: id: type: string type: type: string attributes: $ref: '#/components/schemas/me_attributes' errors_unauthorized: type: object properties: errors: type: array items: $ref: '#/components/schemas/errors_attributes' errors_forbidden: type: object properties: errors: type: array items: $ref: '#/components/schemas/errors_attributes' me_attributes: type: object properties: initials: type: string name: type: string email: type: string role_level: type: string errors_attributes: type: object properties: status: type: string source: type: object nullable: true properties: pointer: type: string title: type: string detail: type: string securitySchemes: Bearer: type: http scheme: bearer ````