> ## Documentation Index > Fetch the complete documentation index at: https://dify-6c0370d8-fix-template-upload-size-guidance.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Get End User Info > **Available for**: Chatflow, Workflow, Agent, Chatbot, Legacy Agent, Text Generator apps. Returns an end user's details by ID. Useful for resolving an end-user ID returned by another endpoint, such as `created_by` in the [Upload File](/en/api-reference/files/upload-file) response. ## OpenAPI ````yaml /en/api-reference/openapi_service.json get /end-users/{end_user_id} openapi: 3.0.1 info: description: >- REST API for Dify applications and knowledge bases. Application endpoints authenticate with an app API key; knowledge endpoints authenticate with a dataset API key. title: Dify Service API version: 1.0.0 servers: - description: >- Base URL of the Dify Service API. For self-hosted deployments, replace it with your own API base URL. url: https://{api_base_url} variables: api_base_url: default: api.dify.ai/v1 description: Host and path of the API base URL, without the `https://` prefix. security: - ApiKeyAuth: [] tags: - description: Operations related to chat messages and interactions. name: Chat Messages - description: File upload and preview operations. name: Files - description: Operations related to end user information. name: End Users - description: User feedback operations. name: Feedback - description: Operations related to managing conversations. name: Conversations - description: Text-to-Speech and Speech-to-Text operations. name: Audio - description: Operations to retrieve application settings and information. name: Applications - description: Operations related to managing annotations for direct replies. name: Annotations - description: Endpoints for resuming paused workflows that require human input. name: Human Input - description: Operations for executing and managing workflows. name: Workflow Runs - description: Operations related to text generation and completion. name: Completion Messages - description: >- Operations for managing knowledge bases, including creation, configuration, and retrieval. name: Knowledge Bases - description: >- Operations for creating, updating, and managing documents within a knowledge base. name: Documents - description: Operations for managing document chunks and child chunks. name: Chunks - description: >- Operations for managing knowledge base metadata fields and document metadata values. name: Metadata - description: Operations for managing knowledge base tags and tag bindings. name: Tags - description: Operations for retrieving available models. name: Models - description: >- Operations for managing and running knowledge pipelines, including datasource plugins and pipeline execution. name: Knowledge Pipeline paths: /end-users/{end_user_id}: get: tags: - End Users summary: Get End User Info description: >- **Available for**: Chatflow, Workflow, Agent, Chatbot, Legacy Agent, Text Generator apps. Returns an end user's details by ID. Useful for resolving an end-user ID returned by another endpoint, such as `created_by` in the [Upload File](/en/api-reference/files/upload-file) response. operationId: getEndUserChat parameters: - description: ID of the end user to look up. in: path name: end_user_id required: true schema: format: uuid type: string responses: '200': content: application/json: examples: endUserDetail: summary: Response Example value: app_id: a1b2c3d4-5678-90ab-cdef-1234567890ab created_at: '2024-01-16T12:00:29Z' external_user_id: abc-123 id: f1e2d3c4-b5a6-7890-abcd-ef1234567890 is_anonymous: false name: null session_id: abc-123 tenant_id: 11223344-5566-7788-99aa-bbccddeeff00 type: service-api updated_at: '2024-01-16T12:00:29Z' schema: $ref: '#/components/schemas/EndUserDetail' description: End user retrieved successfully. '404': content: application/json: examples: end_user_not_found: summary: end_user_not_found value: code: end_user_not_found message: End user not found. status: 404 description: '`end_user_not_found` : End user not found.' components: schemas: EndUserDetail: properties: app_id: description: Application ID. format: uuid nullable: true type: string created_at: description: Creation timestamp. format: date-time type: string external_user_id: description: >- The `user` identifier provided in API requests (e.g., the `user` field in [Send Chat Message](/en/api-reference/chat-messages/send-chat-message)). nullable: true type: string id: description: End user ID. format: uuid type: string is_anonymous: description: >- Whether the user is anonymous. `true` when no `user` identifier was provided in the original API request. type: boolean name: description: End user name. nullable: true type: string session_id: description: Session identifier. Defaults to the `external_user_id` value. type: string tenant_id: description: Tenant ID. format: uuid type: string type: description: End user type. Always `service-api` for Service API users. type: string updated_at: description: Last update timestamp. format: date-time type: string type: object securitySchemes: ApiKeyAuth: bearerFormat: API_KEY description: >- Every request authenticates with an API key: `Authorization: Bearer {API_KEY}`. App endpoints take an app API key; knowledge endpoints take a knowledge base API key ([Get Started](/en/api-reference/guides/get-started)). Keep keys server-side; never embed them in client code. Requests with a missing or invalid key fail with HTTP `401` (`unauthorized`). scheme: bearer type: http ````