This project demonstrates API Chaining for CRUD operations using the Restful-Booker API.
API Chaining means using the response of one API as input for the next, mimicking real-world workflows like authentication → create → read → update → delete.
- Authentication – Get access token
- Create – Create a booking and capture
bookingid - Read – Retrieve booking details using
bookingid - Update – Modify booking using
bookingid+token - Delete – Remove booking using
bookingid+token
- Postman – API Testing & Chaining
- JavaScript Tests – Postman test scripts for validation
- Environment Variables – Store
tokenandbookingiddynamically - REST API – Restful-Booker
sequenceDiagram
participant U as User
participant A as Auth API
participant C as Create Booking
participant G as Get Booking
participant UPT as Update Booking
participant D as Delete Booking
U->>A: POST /auth (username + password)
A-->>U: Returns Token
U->>C: POST /booking (Create)
C-->>U: Returns bookingid
U->>G: GET /booking/{bookingid}
G-->>U: Returns Booking Details
U->>UPT: PUT/PATCH /booking/{bookingid} + Token
UPT-->>U: Returns Updated Details
U->>D: DELETE /booking/{bookingid} + Token
D-->>U: Returns 201 (Deleted)
├── 📘 README.md
├── 📑 API_Chaining.postman_collection.json # Exported Postman collection
├── 🌐 PROD_Environment.postman_environment.json # Postman environment with variables
├── 📊 Newman Reports # Test execution reports (HTML)
- How to perform API Chaining with dynamic variables.
- Validating responses with Postman test scripts.
- Handling CRUD lifecycle in a single automated workflow.
- 📧 Email: sharvarimehta97@gmail.com
- 💼 LinkedIn: linkedin.com/in/sharvarimehta
- 🔗 Postman Profile: postman.com/sharvarimehta