Understanding REST APIs

REST APIs were the bridge between my frontend and backend work. Learning how to design clean, predictable endpoints made full-stack development feel cohesive.

What I Learned

• REST Principles — resources, HTTP methods (GET, POST, PUT, DELETE), and stateless design
• URL Design — consistent URL conventions (GET /api/products, POST /api/reviews, DELETE /api/orders/:id)
• Status Codes — using the right codes (200, 201, 400, 401, 404, 500) for clear communication
• Request/Response Patterns — consistent JSON structures, error formatting, pagination

Building Real Projects

I designed the REST API for Your Place from scratch. Planning the resource hierarchy, implementing CRUD for each entity, and adding authentication middleware taught me how real-world APIs are structured.

Where I Am Now

I design APIs with clear conventions and consistent patterns. REST is my default approach for client-server communication, and I understand the tradeoffs vs GraphQL and other alternatives.