A case for boring APIs

REST is considered old-fashioned in every sense. Yet most of the APIs I trust in production are predictable, well-documented and a little boring.

When a team does need flexibility, I reach for GraphQL. But for public and partner APIs, like the one at Harbor Pay, plain REST with OpenAPI docs wins.

Clear resource names, consistent errors and versioned endpoints age better than almost anything else I design.