API DocsAPI Docs / Auth / Update Me

PUT /api/v1/auth/me

Allows the currently authenticated user to update their own profile information.

Permissions

This endpoint requires authentication but does not require any special permissions. Users can only update their own profile.

Request Body Parameters

Notes:

• All parameters are optional. If omitted, they will not be updated.
• Uploading a trainer license is not done here — use Create Media with attachable_type=user and purpose=trainer_license.
• trainer_license_approved and trainer_license_rejection_reason are operator-only and are not accepted on this endpoint; sending them has no effect.
• Clearing trainer_license_image deletes the stored document and resets the approval back to pending.
• phone cannot be changed here, and that is deliberate. A phone number is an authentication factor on this platform — registration and password reset both key on it — so moving it without OTP re-verification would let anyone holding a hijacked session take over the account. Self-service phone change needs an OTP re-verification flow, which does not exist yet. An operator can change it via PUT /users/{id}.
• is_trainer and is_gym_owner are self-identification, not entitlement. No policy, permission or route middleware reads them. Setting is_trainer to false hides the trainer sections in the app and changes no API outcome — the user keeps every permission, training service and trainee they had. They are settable here and not on PUT /users/{id}, because they are the user's own statement about themself; sending them to the operator endpoint has no effect.
• Email and username must be unique across all users.
• Users can reuse their own current email and username when updating other fields.

Request Example

PUT /api/v1/auth/me
Authorization: Bearer {token}
Content-Type: application/json

{
  "first_name": "John",
  "last_name": "Doe",
  "email": "john.doe@example.com",
  "username": "johndoe",
  "height": 180,
  "birth_date": "1990-05-15",
  "is_trainer": true,
  "is_gym_owner": false
}

Response

200 OK

Returns the updated user resource.

Example

{
  "data": {
    "id": 1,
    "first_name": "John",
    "last_name": "Doe",
    "email": "john.doe@example.com",
    "username": "johndoe",
    "height": 180,
    "gender": "male",
    "birth_date": "1990-05-15",
    "is_trainer": true,
    "is_gym_owner": false,
    "created_at": "2023-01-01T00:00:00.000000Z",
    "updated_at": "2023-01-15T10:30:00.000000Z",
    ...
  }
}

For a full schema, see User Resource.

Error Responses

409 Conflict - Email Already in Use

{
  "error": "This email is already in use."
}

409 Conflict - Username Already in Use

{
  "error": "This username is already in use."
}

422 Validation Error Examples

{
  "message": "The email field must be a valid email address.",
  "errors": {
    "email": ["The email field must be a valid email address."]
  }
}

{
  "message": "The height field must be an integer.",
  "errors": {
    "height": ["The height field must be an integer."]
  }
}

{
  "message": "The birth date field must be a valid date.",
  "errors": {
    "birth_date": ["The birth date field must be a valid date."]
  }
}

Related Resources

• GET /api/v1/auth/me - Get current user information
• User Resource - User resource schema