What is a common mistake with RESTful resource design in Web API?

Action-heavy URLs such as /GetCustomer and inconsistent HTTP semantics create brittle contracts. In practice, the value of this concept comes from understanding where it belongs in the architecture, what problem it solves, and what constraints or tradeoffs it introduces.