Travel API — making resources explicit
A backend learning project with documented listing and booking endpoints.
Start with the resource
A travel application needs a shared understanding of what a listing and a booking mean. This repository documents collection and individual-resource endpoints for both.
The API contract
The README lists GET and POST for collections, then GET, PUT, PATCH, and DELETE for individual listings and bookings. It also points developers to Swagger and ReDoc documentation. Naming routes consistently makes an API easier to explore and integrate.
Questions worth asking
Who may change a booking? Which listing fields are required? How should invalid input and unavailable resources be represented? These are review questions for a reliable API, not claims that every policy has been verified in this project.
What this work represents
An ALX backend exercise in resource-oriented API design and documentation. It is not a live booking service, payment integration endorsement, or production readiness report.