> ## Documentation Index > Fetch the complete documentation index at: https://docs2.petstoreapi.com/llms.txt > Use this file to discover all available pages before exploring further. # Update User > Update user information. Only the logged-in user can perform this operation. ## OpenAPI ````yaml api-reference/modern-petstore-3.1.openapi.json put /users/{id} openapi: 3.1.0 info: title: Modern Petstore API summary: A modern, realistic pet store API demonstrating current best practices description: >- This is a modern Pet Store API based on the OpenAPI 3.2 specification. It demonstrates contemporary API design patterns and best practices including RESTful compliance, proper HTTP methods, structured error responses (RFC 9457), and modern authentication flows. Key features include pet catalog browsing, adoption workflow, order management, user accounts, AI-powered chat advisor, and real-time event notifications via webhooks. The API showcases OpenAPI 3.2 capabilities like hierarchical tags, QUERY HTTP method, OAuth device flow, and server-sent events. Some useful links: - [API Documentation](https://docs.petstoreapi.com) - [Source Code Repository](https://github.com/petstoreapi/PetstoreAPI) - [OpenAPI Specification](https://petstoreapi.com/v1/specs/modern-petstore-3.2.openapi.yaml) version: 1.0.0 contact: name: Petstore API Support url: https://petstoreapi.com/support email: support@petstoreapi.com license: name: MIT identifier: MIT servers: - url: https://api.petstoreapi.com/v1 description: Production server security: - bearerAuth: [] - oauth2: [] tags: - name: Store description: Store operations including orders and inventory - name: Pet description: Pet catalog and management operations - name: Payments description: Payment processing with polymorphic payment sources - name: User description: User account management - name: Chat description: >- AI-powered chat completions with streaming support using Server-Sent Events (SSE) externalDocs: description: Learn more about Chat API url: https://petstoreapi.com/docs/chat - name: Webhooks description: Event-driven webhook notifications (OpenAPI 3.2) externalDocs: description: Learn more about webhooks url: https://petstoreapi.com/docs/webhooks paths: /users/{id}: parameters: - name: id in: path description: Unique identifier for the user required: true example: user_abc123xyz schema: type: string - $ref: '#/components/parameters/TenantID' put: tags: - User summary: Update User description: >- Update user information. Only the logged-in user can perform this operation. operationId: updateUser requestBody: content: application/json: schema: $ref: '#/components/schemas/User' example: firstName: Jeffrey lastName: Kris email: jeffrey.kris@example.com phone: '+18634063542' responses: '200': description: User updated successfully. content: application/json: schema: type: object properties: {} headers: {} '400': $ref: '#/components/responses/BadRequest' '404': $ref: '#/components/responses/NotFound' '422': $ref: '#/components/responses/UnprocessableEntity' deprecated: false security: [] components: parameters: TenantID: name: X-Tenant-ID in: header description: >- Optional tenant identifier for data isolation. When provided, all operations will be scoped to this tenant, ensuring data separation between different organizations or users. If omitted, operations will access the shared/public data pool where data may be visible to and modified by other users. required: false schema: type: string format: uuid examples: organization: value: 550e8400-e29b-41d4-a716-446655440000 summary: Organization tenant ID development: value: 7c9e6679-7425-40de-944b-e07fc1f90ae7 summary: Development environment production: value: 9b5e4f89-3c12-4a5e-9f8e-2d3c5a7e6b1a summary: Production environment schemas: User: type: object description: User account information required: - id - username - email - firstName - lastName - createdAt - updatedAt properties: id: type: string format: uuid readOnly: true description: Unique user identifier (UUID v7) examples: - 019b4138-e0af-70b9-8f0c-6ea97d495dfa - 019b4128-6a6b-777c-9ae8-335e962c68d8 username: type: string description: Unique username for login minLength: 3 maxLength: 50 examples: - johndoe - mysqluser email: type: string format: email description: User email address examples: - user@example.com - john.doe@petstore.com firstName: type: string description: User's first name examples: - John - Jane lastName: type: string description: User's last name examples: - Doe - Smith phone: type: string pattern: ^\+?[1-9]\d{1,14}$ description: Phone number in E.164 format examples: - '+12025551234' createdAt: type: string format: date-time readOnly: true description: Account creation timestamp (RFC 3339) examples: - '2025-12-21T13:56:23Z' - '2025-11-15T08:30:00Z' updatedAt: type: string format: date-time readOnly: true description: Account last update timestamp (RFC 3339) examples: - '2025-12-21T13:56:23Z' - '2025-12-21T15:30:45Z' tenantId: type: string format: uuid readOnly: true description: >- Optional tenant identifier for data isolation. When present, indicates this user belongs to a specific tenant. Null or omitted means the user is in the shared/public data pool. examples: - 550e8400-e29b-41d4-a716-446655440000 - 7c9e6679-7425-40de-944b-e07fc1f90ae7 nullable: true preferences: type: object properties: newsletter: type: boolean description: Whether to receive newsletter emails notifications: type: boolean description: Whether to receive notification emails unevaluatedProperties: false unevaluatedProperties: false Error: type: object description: RFC 9457 Problem Details for HTTP APIs required: - type - title - status properties: type: type: string format: uri description: A URI reference that identifies the problem type examples: - https://petstoreapi.com/errors/not-found - https://petstoreapi.com/errors/validation-error title: type: string description: A short, human-readable summary of the problem examples: - Resource Not Found - Validation Error status: type: integer description: The HTTP status code examples: - 404 - 400 - 422 detail: type: string description: A human-readable explanation specific to this occurrence examples: - The requested pet with ID '123' was not found instance: type: string format: uri description: A URI reference that identifies the specific occurrence examples: - /v1/pets/123 errors: type: array description: Detailed validation errors (for 422 responses) items: type: object required: - field - message properties: field: type: string description: The field that failed validation message: type: string description: Description of the validation error code: type: string description: Machine-readable error code unevaluatedProperties: false unevaluatedProperties: false responses: BadRequest: description: Bad request - Invalid parameters headers: RateLimit-Limit: $ref: '#/components/headers/RateLimit-Limit' RateLimit-Remaining: $ref: '#/components/headers/RateLimit-Remaining' RateLimit-Reset: $ref: '#/components/headers/RateLimit-Reset' content: application/problem+json: schema: $ref: '#/components/schemas/Error' examples: invalid-parameter: summary: Invalid query parameter value: type: https://petstoreapi.com/errors/bad-request title: Bad Request status: 400 detail: >- Invalid value for parameter 'status'. Must be one of: available, pending, sold. instance: /pets NotFound: description: Resource not found content: application/problem+json: schema: $ref: '#/components/schemas/Error' examples: pet-not-found: summary: Pet not found value: type: https://petstoreapi.com/errors/not-found title: Not Found status: 404 detail: The requested pet with ID '123' was not found. instance: /pets/123 UnprocessableEntity: description: Unprocessable entity - Validation errors content: application/problem+json: schema: $ref: '#/components/schemas/Error' examples: validation-errors: summary: Validation errors value: type: https://petstoreapi.com/errors/validation-error title: Validation Error status: 422 detail: The request body contains validation errors. instance: /pets errors: - field: name message: Pet name is required code: required_field - field: status message: Invalid status value code: invalid_format headers: RateLimit-Limit: description: The maximum number of requests allowed in the current time window schema: type: integer example: 100 RateLimit-Remaining: description: The number of requests remaining in the current time window schema: type: integer example: 95 RateLimit-Reset: description: The time at which the current rate limit window resets (Unix timestamp) schema: type: integer example: 1702648800 securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- Bearer token authentication using JWT (JSON Web Token). Include the token in the Authorization header as: `Authorization: Bearer ` oauth2: type: oauth2 description: >- OAuth 2.0 authorization with multiple flows including device authorization for IoT devices and smart TVs flows: authorizationCode: authorizationUrl: https://auth.petstoreapi.com/authorize tokenUrl: https://auth.petstoreapi.com/token refreshUrl: https://auth.petstoreapi.com/refresh scopes: read:pets: Read pet information write:pets: Create and update pets read:orders: Read order information write:orders: Create and manage orders read:user: Read user profile write:user: Update user profile chat:write: Access AI chat completions ````