Swagger-style OpenAPI Reference

Review endpoints, parameters, headers, request bodies, response schemas, and examples before practicing in the QA Lab.

Base information

Base URL

https://lab.hakdogan.com

Auth type

Bearer token

Content type

application/json

Version

1.0.0

Endpoints

OpenAPI paths grouped by tag

Description

Retrieve one user profile and validate the contract used by account and admin screens.

Parameters

Name	In	Type	Required	Description
id	path	string	Yes	User identifier, for example u-1001.

Headers

Name	Example	Required	Description
Authorization	Bearer qa-training-token	Yes	Authenticated QA training token.
Accept	application/json	Yes	Client expects JSON.

Request body example

No request body

Response examples

200Successful response

{
  "id": "u-1001",
  "email": "alex@hakdogan.com",
  "role": "qa",
  "isActive": true,
  "lastLogin": "2026-05-02T21:18:00Z"
}

400Error response

{
  "error": "bad_request",
  "message": "Request parameters are invalid"
}

Response schema

Field	Type	Required	Description
id	string	Yes	Stable user id.
email	string	Yes	Primary account email.
role	string	Yes	Current permission role.
isActive	boolean	Yes	Boolean flag used by UI badges.
lastLogin	string	Yes	ISO timestamp shown in audit history.

Try it out

Execute a reference example using the documented contract.

Request URLHeaders

{
  "Authorization": "Bearer qa-training-token",
  "Accept": "application/json"
}

Schemas

User schema

Field	Type	Required	Description
id	string	Yes	Stable user identifier.
email	string	Yes	Primary email address.
role	string	Yes	Permission role such as user, qa, or admin.
isActive	boolean	Yes	Current account activation state.
lastLogin	string	Yes	ISO timestamp for most recent login.