title: Place API key in Headers or URL
body: <p>I'm designing a public API to my company's data. We want application developers to sign up for an API key so that we can monitor use and overuse.</p>
  
  <p>Since the API is REST, my initial thought is to put this key in a custom header. This is how I've seen Google, Amazon, and Yahoo do it. My boss, on the other hand, thinks the API is easier to use if the key becomes merely a part of the URL, etc. "<a href="http://api.domain.tld/longapikey1234/resource" rel="noreferrer">http://api.domain.tld/longapikey1234/resource</a>". I guess there is something to be said for that, but it violates the principle of the URL as a simple address of what you want, and not how or why you want it.</p>
  
  <p>Would you find it logical to put the key in the URL? Or would you rather not have to manually set HTTP headers if writing a simple javascript frontend to some data?</p>