Get Current User

Retrieves the currently authenticated user information

GET /api/users

Get Current User

cURL

curl --request GET \
  --url https://api.example.com/api/users

200

{
  "status": "<string>",
  "data": {
    "user": {
      "id": 123,
      "fullname": "<string>",
      "email": "<string>"
    }
  }
}

Overview

This endpoint returns the profile information of the currently authenticated user. It requires a valid authentication session with the accessToken cookie.

This endpoint requires authentication. You must be logged in with a valid access token cookie.

Authentication

This endpoint uses cookie-based authentication and requires:

• deserializeToken middleware - Extracts and verifies the JWT token from the accessToken cookie
• requiredLogin middleware - Ensures the user is authenticated before accessing the endpoint

The access token is automatically set in your cookies when you successfully register or login.

Request

No request body or query parameters are required. The user information is extracted from the authenticated session.

Response

status · string · required

Response status. Always returns "success" for successful requests.

data · object · required

Contains the user data object.

Show data properties

user · object · required

The authenticated user’s information.

Show user properties

id · number · required

Unique identifier for the user.

fullname · string · required

The user’s full name.

email · string · required

The user’s email address.

Examples

Request

cURL

curl --request GET \
  --url https://juadah-backend.vercel.app/api/users \
  --header 'Cookie: accessToken=your_access_token_here'

Response

200 - Success

{
  "status": "success",
  "data": {
    "user": {
      "id": 1,
      "fullname": "zulfikar",
      "email": "[e-mail]"
    }
  }
}

Error Responses

Status Code	Description
401	User is not authenticated. Access token is missing or expired.
400	Invalid or malformed access token.

Implementation Details

From the handler implementation (src/user/handler.ts:6):

The endpoint retrieves user data from res.locals.user, which is populated by the deserializeToken middleware after successfully validating the JWT token from the accessToken cookie.

The access token cookie is HttpOnly for security and is automatically included in requests when using credentials: 'include' in fetch or similar settings in other HTTP clients.

Related Endpoints

• Register - Create a new account and receive authentication cookies
• Login - Login to an existing account
• Refresh Token - Renew your access token