Version 1.0 | Prepared by Filip Jelinek
| Item | Details |
|---|---|
| Project | Restful Booker API Testing |
| Sprint | Sprint 2 – Authentication |
| Endpoint | POST /auth |
| Version | 1.1 |
| Status | Completed |
| Author | Filip Jelinek |
| Last Updated | July 2026 |
The purpose of this document is to analyze the Authentication endpoint of the Restful Booker API before designing test scenarios, test cases, and Postman requests.
The analysis identifies:
This document serves as the technical foundation for Sprint 2.
| Property | Value |
|---|---|
| Endpoint | /auth |
| HTTP Method | POST |
| Authentication Required | No |
| Content-Type | application/json |
| Response Format | application/json |
The endpoint authenticates a user using a username and password.
If the credentials are valid, the API returns an authentication token.
The generated token is later used to authorize protected endpoints:
| Header | Required | Expected Value |
|---|---|---|
| Content-Type | Yes | application/json |
{
"username": "admin",
"password": "password123"
}| Property | Type | Required | Description |
|---|---|---|---|
| username | String | Yes | User login name |
| password | String | Yes | User password |
Example:
{
"token": "abc123456789"
}| Property | Type | Description |
|---|---|---|
| token | String | Authentication token used for protected requests |
Client
│
▼
POST /auth
│
▼
Validate Credentials
│
▼
Generate Token
│
▼
Return Token
│
▼
Store Token
│
▼
Use Token for Protected Requests
The endpoint should:
The endpoint should be tested with:
The response should be validated for:
Expected successful response:
200 OK
Negative responses should be documented during testing because the public documentation does not define every error condition.
The generated token is expected to:
The documentation does not define:
These represent exploratory testing opportunities.
Potential risks include:
The published documentation does not specify:
These gaps should be documented during execution instead of assumed.
The endpoint requires:
The generated authentication token should be extracted dynamically and stored as an environment or collection variable for subsequent protected requests.
POST /auth
│
▼
Generate Token
│
▼
Store Token
│
▼
PUT /booking/{id}
PATCH /booking/{id}
DELETE /booking/{id}
The Authentication endpoint is the entry point for all protected operations within the Restful Booker API.
Although the endpoint itself is relatively simple, it introduces one of the project’s most important dependencies because the generated authentication token is required for subsequent update and delete operations.
The endpoint should therefore be validated not only for successful authentication but also for response structure, token usability, input validation, and consistency with the documented API contract.
Prepared by: Filip Jelinek
Role: QA Tester
Version: 1.1
Status: Completed