Require that our OpenAPI paths follow one consistent rule about trailing slashes, and I strongly prefer no trailing slash so that /orders and /orders/ never become two subtly different things. I have chased 404s and duplicated cache entries that all traced back to a stray slash that some routers treat as significant and others silently redirect. Picking one convention and enforcing it across every path removes an entire category of consumer confusion and gateway misconfiguration. This is a tiny detail, but consistency in the small things is exactly what separates a polished API from a frustrating one.
Path Trailing Slashes (OpenAPI)
Strategies
APIs Follow Consistent Design Patterns
All APIs must follow consistent design patterns for naming conventions, media types, pagination, filtering, sorting, and error handling, ensuring that consumers can learn patterns once and apply th...
Experiences
Consistency
Achieving consistency in the design, delivery, and maintenance of HTTP APIs across an enterprise is a significant challenge—one that often complicates API operations. Small differences, such as var...
Contracts
Every API is a contract, and the contract experience is about how clearly the promises between provider and consumer are expressed. Technical contracts like OpenAPI and AsyncAPI describe what the A...
Developer Experience
Developer experience is the sum of every interaction a developer has with an API, from the first time they land on the portal to the hundredth time they call an endpoint in production. It covers do...
Lifecycle
design_services Design Design
Design is where the human experience of an API is won or lost. I work design-first, shaping the paths, schema, errors, and naming in the contract before development begins, so that consistency is b...
gavel Terms of Service Production
The terms of service are the legal contract sitting behind the technical one. Clear terms set the expectations between provider and consumer about acceptable use, liability, and change. I want the ...
