The best API is often the one a new engineer can understand before their second cup of coffee.
Explicit beats clever
An API should make the important questions obvious: what can fail, what is required, and what happens next. Typed inputs, predictable status codes, and stable resource names create a shared language between the product and the infrastructure.
Boring is a feature
Queues, relational databases, logs, and small services are not exciting in isolation. They are valuable because they are easy to operate when the system is tired, traffic is uneven, or the person on call is unfamiliar with the codebase.
Good engineering is often the discipline to keep the sharp edges visible.