title: Hyphen, underscore, or camelCase as word delimiter in URIs?
body: <p>I'm designing an HTTP-based API for an intranet app. I realize it's a pretty small concern in the grand scheme of things, but: <strong>should I use hyphens, underscores, or camelCase to delimit words in the URIs?</strong></p>
  <hr />
  <p>Here are my initial thoughts:</p>
  <p><strong>camelCase</strong></p>
  <ul>
  <li>possible issues if server is case-insensitive</li>
  <li>seems to have fairly widespread use in query string keys (<a href="http://api.example.com?**searchQuery**=..." rel="noreferrer">http://api.example.com?**searchQuery**=...</a>), but not in other URI parts</li>
  </ul>
  <p><strong>Hyphen</strong></p>
  <ul>
  <li>more aesthetically pleasing than the other alternatives</li>
  <li>seems to be widely used in the path portion of the URI</li>
  <li>never seen hyphenated query string key in the wild</li>
  <li><em>possibly</em> better for SEO (this may be a myth)</li>
  </ul>
  <p><strong>Underscore</strong></p>
  <ul>
  <li>potentially easier for programming languages to handle</li>
  <li>several popular APIs (Facebook, Netflix, <strike>StackExchange</strike>, etc.) are using underscores in all parts of the URI.</li>
  </ul>
  <p>I'm leaning towards underscores for everything. The fact that most of the big players are using them is compelling (see <a href="https://stackoverflow.com/a/608458/360570">https://stackoverflow.com/a/608458/360570</a>).</p>