Case study · iSeatz
A typed API layer with consistent error handling
Giving every feature one typed, predictable way to call backend services, building on earlier work standardizing GraphQL contracts.
TypeScript
- REST
GraphQL
Problem
Features integrated backend APIs in their own ways, with different request code, loading states and error handling. The same failure could look different, or be missed, depending on which part of the app hit it.
Context
- Earlier, as a Software Engineer on Checkout, I standardized frontend–backend contracts on GraphQL, aligning queries, loading states, error handling and business rules.
- The Next.js platform needed the same consistency for every brand and feature that talks to backend services.
Constraints
- The layer is shared code, so it has to serve many features and brands without special cases leaking in.
- Error handling has to be safe for checkout: useful to engineers, without exposing personal data.
Technical approach
- A reusable integration layer with typed requests and responses, so mistakes show up at compile time.
- A standard error shape and handling path, so features treat failures the same way.
My contribution
- Built the reusable typed API integration layer and its standardized error handling.
- Earlier, brought nearly 67% of GraphQL contracts onto one implementation model.
Written from my own work. Proprietary code, internal system names and confidential business details are left out.